i recently tried to update my huawei p8 lite to android marshmallow 6.0
i unrooted and my bootloader is unlocked.
as the phone rebooted to finalize the installation it rebooted immediatly at 0% and kept rebooting and showing "huawei software installing 0%".
i managed to boot it in fastbootmode but everytime i try to reflash or do anything with it i get the error "remote:command not allowed"
every time i reboot or drain the battery it just goes to the "huawei software installing 0%" screen and starts the loop anew.
how to fix this? or should i just return it to them?
Try this post, start with 1 that should be enough :
http://forum.xda-developers.com/p8lite/general/huawei-p8-lite-android-6-0-marshmallow-t3309796
You can also download the file from this post and try installing the stock recovery:
http://forum.xda-developers.com/p8lite/help/upgrade-android-5-1-1-b008-ale-21-t3285993
olrak said:
Try this post, start with 1 that should be enough :
http://forum.xda-developers.com/p8lite/general/huawei-p8-lite-android-6-0-marshmallow-t3309796
You can also download the file from this post and try installing the stock recovery:
http://forum.xda-developers.com/p8lite/help/upgrade-android-5-1-1-b008-ale-21-t3285993
Click to expand...
Click to collapse
i cant do anything with fastboot. everytime i try to flash or even view something it says (remote:command not allowed)
Try reinstalling your drivers from your computer.
Remove the driver for the fastboot device and try to reinstall them. Use a good resource for the drivers. Like google or huawei etc.
You can also try to download HiSuite 4.04.301 en try system recovery.
olrak said:
Try reinstalling your drivers from your computer.
Remove the driver for the fastboot device and try to reinstall them. Use a good resource for the drivers. Like google or huawei etc.
You can also try to download HiSuite 4.04.301 en try system recovery.
Click to expand...
Click to collapse
i cant use hisuite because my phone is in a bootloop and i cant install new drivers because it says (remote:command not allowed) everytime i try to do something even remotely related to my phone in fastboot
hisuite, oké
install new drivers = on your computer, not on your phone.
when you are in fastboot, go to your computer settings and remove the fastboot device or update the drivers for that device.
olrak said:
hisuite, oké
install new drivers = on your computer, not on your phone.
when you are in fastboot, go to your computer settings and remove the fastboot device or update the drivers for that device.
Click to expand...
Click to collapse
installed new drivers still cant issue any commands
olrak said:
hisuite, oké
install new drivers = on your computer, not on your phone.
when you are in fastboot, go to your computer settings and remove the fastboot device or update the drivers for that device.
Click to expand...
Click to collapse
i think usb debugging is disabled does that have any impact on the situation?
That's not an issue, usb debugging is only necessary when you can startup to android. Try googling, whill do that too.
xileftrepur said:
i recently tried to update my huawei p8 lite to android marshmallow 6.0
i unrooted and my bootloader is unlocked.
as the phone rebooted to finalize the installation it rebooted immediatly at 0% and kept rebooting and showing "huawei software installing 0%".
i managed to boot it in fastbootmode but everytime i try to reflash or do anything with it i get the error "remote:command not allowed"
every time i reboot or drain the battery it just goes to the "huawei software installing 0%" screen and starts the loop anew.
how to fix this? or should i just return it to them?
Click to expand...
Click to collapse
Is the bootloader unlocked?
If not, you'll need to unlock it first in Fastboot (you can use DCUnlocker for it, if you don't want to wait the 14 days for Huawei to do it).
Same Problem.
Exactly the same problem.
I've already posted into the other topic, but I post it here as well.
daviddosa said:
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Edit:
Just saw your post under the other similar topic.
You should try to do a Factory Reset, by hand, via fastboot, and then updating with the "dload" method again.
The commands are:
fastboot erase cache
fastboot erase userdata
Maybe this helps.
Click to expand...
Click to collapse
Related
Hi,, I need help, don't now what to do, I run King root on my phone, xt1562, and **** up everything.... you can see in the pics.. I search, and I can find solution, so please somebody give me the solution for this problem. I tray with adb, mfasboot, rds life to refresh on lollipop without results.
Not sure if i understand your problem, but have you tried to flash twrp to be able to boot in recovery and then flash a rom
you need to unlock your device first then flash twrp recovery , and install supersu to root the device.
try this: http://forum.xda-developers.com/moto-x-play/general/untested-how-to-root-moto-x-play-t3211941
I tray that, but don't work for me, before I start with King root I alow OEM unlock on the developer settings on the phone, and now Adb don't recognize that and ask for OEM unlock, and it impossible now cos phone don't work
lapena said:
I tray that, but don't work for me, before I start with King root I alow OEM unlock on the developer settings on the phone, and now Adb don't recognize that and ask for OEM unlock, and it impossible now cos phone don't work
Click to expand...
Click to collapse
Flash factory firmware, it's pretty much the only thing you can do with locked bootloader. And don't use kingroot any more
minimale_ldz said:
Flash factory firmware, it's pretty much the only thing you can do with locked bootloader. And don't use kingroot any more
Click to expand...
Click to collapse
I try that last 7days with no success, that's why I'm posting this, if you now some link that will be great. Tnx
lapena said:
I try that last 7days with no success, that's why I'm posting this, if you now some link that will be great. Tnx
Click to expand...
Click to collapse
Did you originally have Lollipop or MM. Here's MM firmware:
If it's european XT1562, single sim, try this one:
http://www.filefactory.com/file/1ub...MPD24.107-52_cid7_subsidy-DEFAULT_CFC.xml.zip
If it's asian, dual sim, this one:
http://www.filefactory.com/file/49g...MPD24.107-70_cid7_subsidy-DEFAULT_CFC.xml.zip
(double check it, for you own safety)
Make sure you've got moto drivers and use fastboot or mfastboot.
What messages did you get when flashing before, what did it say exactly after executing fastboot commands?
Tnx
Before, phone was originally on lollipop, and receive Ota update on MM6. 0.1.
I tried to root this phone through this bull**** Kingroot.. And it failed.. Later on when i restarted the phone it got bootlooped and is totally bricked! i get this error- Startup Failed: Your device didn't start up successfully. use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot flashmode (secure)
Fastboot Reason: Last time flashing failed
hab check failed for boot
failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation. backup to fastboot
Boot Up failed
I try with fastboot, and rds lite, computer show connection like adb devices, but when I try to flash, said failed, and rds don't show anethyng, don't recognize phone.
lapena said:
Before, phone was originally on lollipop, and receive Ota update on MM6. 0.1.
I tried to root this phone through this bull**** Kingroot.. And it failed.. Later on when i restarted the phone it got bootlooped and is totally bricked! i get this error- Startup Failed: Your device didn't start up successfully. use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot flashmode (secure)
Fastboot Reason: Last time flashing failed
hab check failed for boot
failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation. backup to fastboot
Boot Up failed
I try with fastboot, and rds lite, computer show connection like adb devices, but when I try to flash, said failed, and rds don't show anethyng, don't recognize phone.
Click to expand...
Click to collapse
If you installed MM OTA you can't flash Lollipop firmware, it must be MM (generally speaking). Get into bootloader and try to flash MM with fastboot.
minimale_ldz said:
If you installed MM OTA you can't flash Lollipop firmware, it must be MM (generally speaking). Get into bootloader and try to flash MM with fastboot.[/QUOTE
Thats the problem..look at adeded pictures in first post...
Click to expand...
Click to collapse
lapena said:
Hi,, I need help, don't now what to do, I run King root on my phone, xt1562, and **** up everything.... you can see in the pics.. I search, and I can find solution, so please somebody give me the solution for this problem. I tray with adb, mfasboot, rds life to refresh on lollipop without results.
Click to expand...
Click to collapse
Check this out, this guy had the same problem and report here if it worked, it'll help others.
http://forum.xda-developers.com/showpost.php?p=68813881&postcount=43
lapena said:
minimale_ldz said:
If you installed MM OTA you can't flash Lollipop firmware, it must be MM (generally speaking). Get into bootloader and try to flash MM with fastboot.[/QUOTE
Thats the problem..look at adeded pictures in first post...
Click to expand...
Click to collapse
I can see it boots in fastboot mode, which is good, but your firmware is messed. Is your phone sim-free or carrier branded? If it's sim-free you should be able to flash the firmware I linked.
Click to expand...
Click to collapse
Tnx
Yes it's Sim free xt1562, model SM4232AD1T1, belive me I try everything, adb, or rds, or mfasboot., don't recognize device, in device list on comp. It's listed something like Fastbot lux... Windows 7.
Tnx, one more time for you will to help.
lapena said:
Yes it's Sim free xt1562, model SM4232AD1T1, belive me I try everything, adb, or rds, or mfasboot., don't recognize device, in device list on comp. It's listed something like Fastbot lux... Windows 7.
Tnx, one more time for you will to help.
Click to expand...
Click to collapse
OK, I guess you installed drivers for it, but maybe reinstall. They're here:
https://motorola-mobility-en-xp.custhelp.com/app/answers/detail/a_id/89880
Can you tell what exactly it says when you enter
Code:
fastboot devices
in command window?
Tnx
When I type that command just display some numbers... Am not at home now, so I can't post number
lapena said:
When I type that command just display some numbers... Am not at home now, so I can't post number
Click to expand...
Click to collapse
if it displays something like this:
Code:
30D41467 FASTBOOT
Then I guess you're good to go with flashing firmware
That's number and text what I got on display, but when I tray next kommand, Fastbot failed.. What to do...for example I typed command fastbot OEM fb_mode_set. On display have this line
(bootloader) slot-count:notfound
(bootloader) slot-suffix:not found
(bootloader) slot-suffix:not found
FAED(remote failure)
lapena said:
That's number and text what I got on display, but when I tray next kommand, Fastbot failed.. What to do...
Click to expand...
Click to collapse
what's the next command you try?
---------- Post added at 20:44 ---------- Previous post was at 20:32 ----------
lapena said:
That's number and text what I got on display, but when I tray next kommand, Fastbot failed.. What to do...for example I typed command fastbot OEM fb_mode_set. On display have this line
(bootloader) slot-count:notfound
(bootloader) slot-suffix:not found
(bootloader) slot-suffix:not found
FAED(remote failure)
Click to expand...
Click to collapse
Did you try to skip this one and start with flashing gpt.bin and then just do the minimum, like here:
http://forum.xda-developers.com/showpost.php?p=62708260&postcount=5
(you may have more sparsechunks to flash, so check their number)
Tnx
Of course I am, and same thing happened... I'm going crazy...
lapena said:
Of course I am, and same thing happened... I'm going crazy...
Click to expand...
Click to collapse
Did you try to skip first 2 commands (gpt and bootloader) and start from
Code:
fastboot flash logo logo.bin
?
Get rid of shutting down after "device corrupt" message - so possibility to gain root
Some of you might face the problem that whatever you do anything you change on your device in order to gain root even if your bootloader is unlocked your device is turning off after promting "device corrupt, etc..." message.
Sometimes you can't even unbrick with lg bridge cos' it can't see that your firmware has any problems.
Typical symptom of this problem that very interestingly your phone is not showing any corrupt messages during normal boot up even if your bootloader is unlocked (it should write some warnig message at every boot up).
Also when you "fastboot boot yourstockbootimage.img" it's booting up but writing some network related error then shuts down saying corrupt battery.
In order to root your phone you must be able to change the firmware a bit (tweak the boot image).
First of all you need to unlock your bootloader if you didn't do it yet: http://forum.xda-developers.com/lg-k10/how-to/unlock-bootloader-lg-k10-mtk-devices-t3486302
All you have to do is allow modifications in TWRP step 2.1 here: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
It means the rest written under is fully unnecessary but i keep it just in case the above mentioned method would not work for someone:
Other requirements:
- lg up working with your device: http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
- kdz firmware
- twrp recovery of your device (usually you can find it in your favorite root thread or somewhere on xda)
Extract boot image from your firmware with lg firmware extractor (http://viid.me/qe7ufH). First you have to extract the ".dz" file and then the boot image form that ".dz" file.
Once you have your boot image (eg. boot_157696.bin) rename it to "boot.img"!
Put this "boot.img" on your sd card!
Flash this firmware (that you taken your boot image form!!!) on your phone with LG UP.
Boot up and see if it works also tick all the necessary options (oem unlock in developer options, usb debug,...)
Reboot to fastboot, check if your bootloader is still unlocked ("fastboot getvar all"). If it's locked unlock it!
Boot into your TWRP (fastboot boot twrp.img), you can allow it to read system.
Go to "install" (tick install image) and flash your "boot.img" form your sd card (naturally onto your boot partition).
Now before you reboot make a full wipe (fastory reset) in TWRP (wipe menu) then you can reboot to system.
After the "device corrupt" message it must be booting on and boot up normally and during every boot up there should be that message.
Now you can go and root your phone - always use that boot image you just flashed during the first step of the root process (recompress this boot image to gzip and ... read a rooting guide: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807 there this should be "bootlz4_0.img")
There is no explanation why it works... wierd.
Hi.
I have this problem, corrupt device screen and continuous bootloops, I only have access to the download mode, but LG UP does not allow me to flash the .kdz even though I have the boot.img file on the sd card. It shows me the typical error at 9% of the process 'Error code = 0x81000304, CBasicFlash :: _func_LoadGptF - ErrorCode: 8222'. Would someone tell me what it is and how can I fix it?
I have tried to revive the cell phone in myriad ways and it is not possible for me.
I appreciate any suggestions.
Thank you very much.
Llony said:
I appreciate any suggestions.
Thank you very much.
Click to expand...
Click to collapse
This thread is not about bootloops but shutting down. Different subject. You should start a new thread about it.
However i looked at it, check out this comment:
http://forum.xda-developers.com/showpost.php?p=66135219&postcount=74
anyways if i were you i'd do a hard reset (http://www.hardreset.info/devices/lg/lg-k10/) and then i'd use lg bridge's update error recovery function (or you can change the order - first lg bridge, then hard reset).
Also make sure you chose "refurbish" when you use lg up and also make sure you are using the right kdz file (i recommend using lg mobile support tool to download your kdz - there is a possibility under options and upgrade recovery that using your imei it downloads the kdz to a hidden folder: http://forum.xda-developers.com/showthread.php?t=2395323)
I have bootloop with usb connected, without usb powered off
Llony said:
I have bootloop with usb connected, without usb powered off
Click to expand...
Click to collapse
I see... okay. However check out what i wrote above and one more thing: make sure you use usb 2.0 not any 3.0 ports.
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Llony said:
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Click to expand...
Click to collapse
Did you try lg bridge - update error recovery?
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Llony said:
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Click to expand...
Click to collapse
What do you mean it doesn't give you the option? I mean LG bridge, there is no update error recovery on the software update page? As in this video:
https://www.youtube.com/watch?v=b_GqAG02OXU
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.
Hello,
I was always a Samsung fanboy, but than I decided to buy the P9 lite (VNS-L21 single sim)
I wanted to flash the android 7 update for my phone, but I was such a noob in Huawei, that I didn't understand a word. But i tried to do what the instructions said. Now my phone is bricked. I can go to recovery, erecovery (which can't download anyithing) and download mode. I heard of this fastboot stuff as well, but I don't know how to do this. I tried to flash as many roms as I could with dload and it didn't work, after 5%, it said it failed... Now I don't know what to do. I think somebody (expert) should make a clear tutorial for noobs. Oh and I almost forgot that i don't have root, custom recovery, and things like that. I just bought the phone, I didn't want to make big changes, just new android. Is it possible that after this Huawei would fix my phone, if I couldn't? Or warranty is void? And sadly I don't know more of my phone because I'm not ina rom, and the phone and papers don't say more.
If you could help me, I would appreciate it:
Raul
Turn off your phone, connect to the pc while holding the volume down button, you will end up in fastboot mode.
I assume you have ADB and drivers installed (if not, install ADB and device drivers).
Optional: unlock your bootloader if it's locked.
Download the latest offical rom zip for your phone version (the marshmallow one), extract the update.app.
Use Huawei extractor to ectract the following files (google is your friend in this one, but its not difficult):
boot.img
recovery.img
cust.img
system.img
After you've done this, connect your phone to the PC in fastboot mode .
Open a command promt from the folder where the extracted files are (shift+right click, Open Command window here), enter the following commands
fastboot devices (you will see the list of attached devices with a lot of random number + fastboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
fastboot reboot
After all this, you should be good to go, just be sure you are using the correct rom for you version.
Or you can just serach on the forum and find this.
https://forum.xda-developers.com/huawei-p9lite/help/unbricking-vns-l21-vns-l31-tutorial-t3583400
(Sorry for my english.)
Fastboot says that it has failed command not alllowed, after I want to installl the files. And I couldn't unlock bootloader without phones information...
rr999999 said:
I would happily unlock my bootloader, but I don't know anyithing about my phone (except model...) without the os...
Click to expand...
Click to collapse
Post here IMEI and SN from the box of phone and i can try get your bootloader unlock code...
If I would unlock it, would fastboot work? Because fastboot pc app recognizes my phone, but my phone says in fastboot mode, that I should connect itself to pc and open hisuite. WTF?
rr999999 said:
If I would unlock it, would fastboot work? Because fastboot pc app recognizes my phone, but my phone says in fastboot mode, that I should connect itself to pc and open hisuite. WTF?
Click to expand...
Click to collapse
Until you have bootloader unlock you can not run any fastboot flash command...
rr999999 said:
If I would unlock it, would fastboot work? Because fastboot pc app recognizes my phone, but my phone says in fastboot mode, that I should connect itself to pc and open hisuite. WTF?
Click to expand...
Click to collapse
Heyho,
normally yes, after bootloader unlock u are able to flash via fastboot. But...
I tried to flash as many roms as I could with dload and it didn't work, after 5%, it said it failed...
Click to expand...
Click to collapse
What is the error? - Have u disconnected the device from the PC during the update?
If not, try to update again and just disconnect the device from any USB connection...
Regards,
Sebastian
k1ll3r8e said:
Heyho,
normally yes, after bootloader unlock u are able to flash via fastboot. But...
What is the error? - Have u disconnected the device from the PC during the update?
If not, try to update again and just disconnect the device from any USB connection...
Regards,
Sebastian
Click to expand...
Click to collapse
Hello. I disconnected it from everything (for example USB)When I tried to install it said something like incompatibility version, but it couldn't be because I tried many roms for my phone. And I tried some dual sim roms as well because, I thought that it might work... But then I will do that unlock if it will do good. Thanks for the help Without bootloader I can't flash from dload as well?
rr999999 said:
Hello. I disconnected it from everything (for example USB)When I tried to install it said something like incompatibility version, but it couldn't be because I tried many roms for my phone. And I tried some dual sim roms as well because, I thought that it might work... But then I will do that unlock if it will do good. Thanks for the help Without bootloader I can't flash from dload as well?
Click to expand...
Click to collapse
Heyho,
the dload method works always without unlock bootloader. But, u can't flash for example an B161 over an B3xx (what nougat is) if the update u installed modified already the oeminfo u are not able to flash any rom below B3xx (nougat) via dload.
-
In that case u might use the official rollback package (never tested it myself) or, u unlock ur bootloader, flash a TWRP recovery matching to ur current FW. Flash from there a oeminfo + custom.bin (lower than B3xx) and flash the FW matching to the new oeminfo via dload and stock recovery.
Regards,
Sebastian
If you have custom recovery, wipe everything. Data, system, boot. extract update app (which is your stock rom) with huawei update extractor. go to custom recovery, flash stock boot IMG and stock recovery IMG. Power off, use three button dload method, reboot, when booting press vol up for three second, now you are in e-recovery. Press shutdown. Press and hold power and vol up for stock recovery. Do factory reset. If need do the factory reset 2/3 times. Now you are with locked bootloader.
Sent from my NEM-L21 using Tapatalk[/QUOTE]
Sent from my NEM-L21 using Tapatalk
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