I have the Chinese version of axon 7 and under development options I can click on OEM unlock then it asks for a pin number. How do I get that pin number?
Have you contacted zte customer service?
Please let me know how this turns out
I've been around these forums multiple times now and the ways that should work don't seem to work for me :/ Can't find a confirmed unlock of the Chinese version and am stuck on B13 while I wany Cyanogen.
If you go and sign up for ztes website and then go to the developers lounge there is a lot of talk about bootloader unlock. The way I read it you could have signed up to receive a pin number to unlock bootloader but zte has put that on hold? But are suppose to start it back up?
you can flash unlock bootloader in port 9008, I unlocked successfully by this way
@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.
enkrs said:
@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.
Click to expand...
Click to collapse
Did you flash twrp ? Official recovery does not support adb.
If you have already flashed twrp, then open computer manager- device manager, you will see your phone doesn‘t work correctly (triangle) , right click on the triangle, and click update driver, then computer will fix this proble automatically.
Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.
Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .
enkrs said:
Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.
Click to expand...
Click to collapse
waiting for device...you should kill adb process first, and then reconnect your pc
---------- Post added at 11:33 ---------- Previous post was at 11:32 ----------
enkrs said:
Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .
Click to expand...
Click to collapse
if you want to downgrade the b13 to the b10，maybe you should use official recovery
If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.
enkrs said:
If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.
Click to expand...
Click to collapse
Hello Mate,
I am in the same situation as you. I have been looking all over the internet and came across a Chinese forum. Apparently, it is possible to unlock and root B13. However, I have used Google translater to translate the page. It's hard to understand the steps. I have not tested it. But maybe someone out there will have a better understanding and could give it a go. Here is the link
http://www.myzte.cn/forum.php?mod=viewthread&tid=320458&mobile=2
Hope that helps
Related
Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.
Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP
Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?
Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?
Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat
Thanks for the guide. I've already recommended it to someone who was having problems.
jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.
Hello Everyone. I need some help with restoring my shield because I seem to have soft-bricked it. Last week I rooted and installed a custom recovery file and all was well but this past weekend I was messing around with it trying to install the custom rom for full android and I think I accidentally deleted the boot file and the recovery file because all I get is the android on his back with the red triangle. Also, when I try to connect to the unit using fastboot nothing is found but I DO get a hit if I put the unit in stock recovery, it gives me the option to click apply update from adb.
From what I have been reading it sounds like I should be able to sideload the recovery and/or the stock firmware. Can anyone confirm or provide me with instructions on how to get this unit back up and running.
Any help is greatly appreciated
Wow I expected people to jump on this one. I guess I'll just keep messing around with it
Hy, here is the firmware and the instructions:
FW:
https://developer.nvidia.com/gameworksdownload (here you will have to scroll down to your console version PRO/non-PRO
Instructions:
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
hpric said:
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
Click to expand...
Click to collapse
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
gffmac said:
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
Click to expand...
Click to collapse
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Beefheart said:
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
Click to expand...
Click to collapse
Correct. I can only use sideload at this time. Yesterday I was messing around with it a little more trying to sideload the recovery but I kept getting a message saying "The footer was incorrect" and it would cancel the install. I tried different files to make sure I wasn't dealing with a corrupted zip file but they all gave the same message.
I'm trying to figure out how to sideload the recovery
Beefheart said:
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Click to expand...
Click to collapse
Correct
Hello, I am facing the exact issue. Please let me know if you figured a way to debrick?
All I can do is ADB sideload and E:footer error keeps coming up.
Help is appricated,
Thanks
Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet
ishmeet said:
Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet
Click to expand...
Click to collapse
FOLLOW THESE INSTRUCTIONS ONLY IF ANYTHING BETTER DOESNT COME UP BECAUSE I DON'T WANT TO FEEL GUILTY IF YOU "FUBAR" YOUR PHONE. I am not an expert in this stuff.. I can only follow instructions and the two videos helped me get out of crappy situation in the past couple weeks.
Follow the two videos below on how to re-install your drivers properly and flash and root Nougat 7.0
First go delete your driver from your PC via Device Manager. Anything that you can associate with N6P or Google.
Then watch this video on how to install new drivers.
This video on how to install Nougat
If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.
Pain-N-Panic said:
If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.
Click to expand...
Click to collapse
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.
ranjha94 said:
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.
Click to expand...
Click to collapse
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
I think I figured out mine problem. I am not sure what you mean by locked bootloader but in my case I was able to reboot to bootloader by pressing all three buttons (Volume up, Volume down and power button) at the same time.
Once you are there and if your bootloader is already unlocked you can flash your own android. Probably this process is called unbrick your phone. I am surprissed and sad as I am not allowed to post link which can help you. Ask admin.
Any related problem while following process. I can try as I am not very expert.
RIP my English.
Thanks
---------- Post added at 05:20 AM ---------- Previous post was at 05:16 AM ----------
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
https://devs-lab.com/how-to-unbrick-hard-soft-bricked-google-huawei-nexus-6p.html
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
And that's why it's a good idea if you do ANY tinkering to your phone that you have an unlocked bootloader. I have screwed my phone up a hundred times over but nothing that a fastboot flash of the stock Google images couldn't overcome.
I'm not sure what situation you're in but I would try to get that bootloader unlocked asap. Just know that when you unlock it, every partition on the phone will be completely wiped to include internal storage (sd card).
I wasn't tinkering that's the thing. I was on the Android beta but I have installed those OTA. I would love to be able to unlock the bootloader but none of the commands will work to unlock it because usb debugging was not enabled or the developer options and I can't boot it to change that.
Hi Guys
I finally manage to unlock my bootloader on my VNS L31 unlocked. I have flashed the TWRP Recovery tool, but I'm stuck on the Booting... text if I press Volume Up and Power. If I do a normal boot, the phone boots as per normal and I can access the OS. After looking around it seems like its because I'm using Android 7.0 - and have tried a few Nougat specific TWRP builds. None of them worked.
Can anyone please point me in the right direction? I'm looking for a TWRP recovery tool that will work, as well as a working root method.
Bonus Question:
What custom ROMs do you guys recommend for the VNS L31?
My experience with the bootloader unlock code that might help some people:
I tried the Huawei request form, but it just gave me errors. I also emailed them twice, but they refused to give me the code. What I ended up doing was using DC Unlocker. It sucked that I had to spend money, but at least it worked... I hope this might save some people from getting super frustrated.
Hi,
It's simpler for you to install directly a custom rom with (include) TWRP recovery and root methode (magisk is cool).
In my personal experience, EliteRom is the best at the moment, the next version was coming soon, please wait (v5) and install.
Advice: reinstall a clean and untouched version of Emui before flashing a custom rom (Elite Rom ).
Follow my guide HERE
EDIT: is not difficult to obtain a OEM code with Huawei website, just try on Chinese version and done!
Good luck!
WitchcraftZA said:
Hi Guys
I finally manage to unlock my bootloader on my VNS L31 unlocked. I have flashed the TWRP Recovery tool, but I'm stuck on the Booting... text if I press Volume Up and Power. If I do a normal boot, the phone boots as per normal and I can access the OS. After looking around it seems like its because I'm using Android 7.0 - and have tried a few Nougat specific TWRP builds. None of them worked.
Can anyone please point me in the right direction? I'm looking for a TWRP recovery tool that will work, as well as a working root method.
Bonus Question:
What custom ROMs do you guys recommend for the VNS L31?
My experience with the bootloader unlock code that might help some people:
I tried the Huawei request form, but it just gave me errors. I also emailed them twice, but they refused to give me the code. What I ended up doing was using DC Unlocker. It sucked that I had to spend money, but at least it worked... I hope this might save some people from getting super frustrated.
Click to expand...
Click to collapse
Flash @OldDroid TWRP from fastboot:
Code:
fastboot flash recovery recoveryname.img
Then reboot to android:
Code:
fastboot reboot
You need to have adb installed on your pc.
I recommend the 15 second ADB installer .
Enable usb debbuging in development settings and give authorization to your pc by confirming the prompt on your phone.
Then using adb reboot to recovery.
Code:
adb reboot recovery
Hope it helps
dariomrk said:
Flash @OldDroid TWRP from fastboot:
Then reboot to android:
You need to have adb installed on your pc.
I recommend the 15 second ADB installer .
Enable usb debbuging in development settings and give authorization to your pc by confirming the prompt on your phone.
Then using adb reboot to recovery.
Hope it helps
Click to expand...
Click to collapse
Thanks dude.
I actually got it working before seeing your post. Bur its basicakly what I did, so you were right on the money.
WitchcraftZA said:
Thanks dude.
I actually got it working before seeing your post. Bur its basicakly what I did, so you were right on the money.
Click to expand...
Click to collapse
Nice to hear you sorted it out
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