Hey, When trying to update software with stock rom and recovery, I cannot update with "installation failed" error. So I wanted to do other things with fastboot, but with fastboot only the bootloader can be unlocked. Errors I get while installing TWRP:
FAILED (remote: Requested download size is more than max allowed)
or
stuck on "sending recovery.img"
Officially I'm stuck in the Oreo 8.1 version. No matter how much research I did on this issue, I could not reach a solution. What I tried are the following
- All resets that can be done on the phone.
- Delete and reinstall ADB
- Refreshing rom and recovery files
- adb sideload
Please help.
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery (file name).img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
---------- Post added at 02:59 AM ---------- Previous post was at 02:39 AM ----------
gokhanhaskilit said:
Hey, When trying to update software with stock rom and recovery, I cannot update with "installation failed" error. So I wanted to do other things with fastboot, but with fastboot only the bootloader can be unlocked. Errors I get while installing TWRP:
FAILED (remote: Requested download size is more than max allowed)
or
stuck on "sending recovery.img"
Officially I'm stuck in the Oreo 8.1 version. No matter how much research I did on this issue, I could not reach a solution. What I tried are the following
- All resets that can be done on the phone.
- Delete and reinstall ADB
- Refreshing rom and recovery files
- adb sideload
Please help.
Click to expand...
Click to collapse
Fastboot boot (filename).img.
It will boot into recovery flash recovery from the recovery.
1)Try to use another usb port in your Pc ,
2)If you still getting those errors reinstall the adb driver may help,
3)Try to clear cache from the existing stock recovery
And execute the command
4)Try renaming the file name (smaller) it's a myth:laugh:
I hope it will fix your problem:good:
[email protected] said:
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery (file name).img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
---------- Post added at 02:59 AM ---------- Previous post was at 02:39 AM ----------
Fastboot boot (filename).img.
It will boot into recovery flash recovery from the recovery.
1)Try to use another usb port in your Pc ,
2)If you still getting those errors reinstall the adb driver may help,
3)Try to clear cache from the existing stock recovery
And execute the command
4)Try renaming the file name (smaller) it's a myth:laugh:
I hope it will fix your problem:good:
Click to expand...
Click to collapse
fastboot erase recovery
fastboot erase cache
When you enter the commands above, it starts but doesn't finish. So it is not Finished. No results were obtained in other operations.
What else can you suggest about this?
gokhanhaskilit said:
fastboot erase recovery
fastboot erase cache
When you enter the commands above, it starts but doesn't finish. So it is not Finished. No results were obtained in other operations.
What else can you suggest about this?
Click to expand...
Click to collapse
Have you tried fastboot boot recovery.img
[email protected] said:
Have you tried fastboot boot recovery.img
Click to expand...
Click to collapse
I tried but failed. Can we talk on Telegram?
gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
Hey. You can't flash anything via fastboot on locked bootloader.
The reason you can't update is that your phone doesn't have vendor partition. Recovery can't find it. That's why it stops. You have to flash Pie stock first (preferably the release that introduced vendor partition (treble), then you can upgrade to Android Q.
gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0
Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat
I'm also looking for a solution for your problem
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
optimumpro said:
Hey. You can't flash anything via fastboot on locked bootloader.
The reason you can't update is that your phone doesn't have vendor partition. Recovery can't find it. That's why it stops. You have to flash Pie stock first (preferably the release that introduced vendor partition (treble), then you can upgrade to Android Q.
Click to expand...
Click to collapse
He already unlocked the bootloader
[email protected] said:
I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0
Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat
I'm also looking for a solution for your problem
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
He already unlocked the bootloader
Click to expand...
Click to collapse
Yes, I guess the problem is in the relationship between ADB and USB 3.0 connectivity.
Desktop PC
Windows 10 Pro 1909
I don't know much about the differences between USB 2.0 and 3.0 but I know the blue ones in the USB port are 3.0 and the black ones are 2.0. Although I have tried all USB ports on the computer, the result does not change. (The problem with USB 2.0 and USB 3.0 is different)
- Minimal ADB and several drivers have been downloaded to this PC for Xioami device. (QUALCOMM, XIOAMI, GOOGLE AND MORE) Is it because they conflict? I tried yesterday on another computer but I am getting the same issue. So I guess the problem isn't just with the PC.
You are right about Telegram. I've tried most operations with my lock on and off. The result does not change.
[email protected] said:
I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0
Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat
I'm also looking for a solution for your problem
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
He already unlocked the bootloader
Click to expand...
Click to collapse
gokhanhaskilit said:
Yes, I guess the problem is in the relationship between ADB and USB 3.0 connectivity.
Desktop PC
Windows 10 Pro 1909
I don't know much about the differences between USB 2.0 and 3.0 but I know the blue ones in the USB port are 3.0 and the black ones are 2.0. Although I have tried all USB ports on the computer, the result does not change. (The problem with USB 2.0 and USB 3.0 is different)
- Minimal ADB and several drivers have been downloaded to this PC for Xioami device. (QUALCOMM, XIOAMI, GOOGLE AND MORE) Is it because they conflict? I tried yesterday on another computer but I am getting the same issue. So I guess the problem isn't just with the PC.
You are right about Telegram. I've tried most operations with my lock on and off. The result does not change.
Click to expand...
Click to collapse
Also fastboot screen says "PRODUCT NAME: qc referance phone". It used to write my device serial number. So I guess I might have messed up something while installing the final ROM. or Drivers ...
gokhanhaskilit said:
Also fastboot screen says "PRODUCT NAME: qc referance phone". It used to write my device serial number. So I guess I might have messed up something while installing the final ROM. or Drivers ...
Click to expand...
Click to collapse
If you want to update your phone use a unbrick tool
(Android pie unbrick tool is available)
https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
This may help to replace your old Oxygen os bootloader with latest one so this may help to fix your issue ,we must hope this one will fix
( Do it at your own risk I am not responsible if anything goes wrong)
[email protected] said:
If you want to update your phone use a unbrick tool
(Android pie unbrick tool is available)
https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
This may help to replace your old Oxygen os bootloader with latest one so this may help to fix your issue ,we must hope this one will fix
( Do it at your own risk I am not responsible if anything goes wrong)
Click to expand...
Click to collapse
OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?
gokhanhaskilit said:
OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?
Click to expand...
Click to collapse
What do you mean cache removal tool?
[email protected] said:
What do you mean cache removal tool?
Click to expand...
Click to collapse
Never mind. A translation error has occurred. My OnePlus 5 device is not recognized by the MSM Download Tool (Unbrick Tool). What should I do?
gokhanhaskilit said:
Never mind. A translation error has occurred. My OnePlus 5 device is not recognized by the MSM Download Tool (Unbrick Tool). What should I do?
Click to expand...
Click to collapse
I switched the device to the PIE version. I tried to flash Nougat rom to try it out right away. However, like in Oreo, the loading screen stops for a while and throws it back to the main screen. Presumably the problem with ADB persists.
I guess our problem is more than unbrick tool ..
gokhanhaskilit said:
I switched the device to the PIE version. I tried to flash Nougat rom to try it out right away. However, like in Oreo, the loading screen stops for a while and throws it back to the main screen. Presumably the problem with ADB persists.
I guess our problem is more than unbrick tool ..
Click to expand...
Click to collapse
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...
gokhanhaskilit said:
OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?
Click to expand...
Click to collapse
gokhanhaskilit said:
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...
Click to expand...
Click to collapse
I don't understand what you talking about
Did you mean you have successfully installed TWRP?.
Did you installed oos9.11 using the unbrick tool successfully?
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
gokhanhaskilit said:
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...
Click to expand...
Click to collapse
Try using the new adb driver
Uninstall older driver and install this:
http://www.mediafire.com/file/a4d0p5uvebc0xwp/file
Related
So yeah I accidentally wiped my partitions as if I were installing a rom. Am I screwed until I get to a pc?
P.s. Out of all days to delete my backup rom file ?
Just set it to boot loader mode and flash stock images...I'm sure there's a tutorial on how to do it..I have the program installed on my computer ready for any time I brick my phone lol but I don't remember the name of the program right now
Edit: heres the link to the method I use http://forum.xda-developers.com/showthread.php?t=3258493
I'm assuming the OP doesn't have a PC due to the last statement he made. I would say yes, nothing you can do until you can get to a PC and flash stock images via Fastboot. Unless you have a ROM zip on your phone that is....which I'm assuming you don't.
You're kinda stuck, you need a PC to flash the factory images. TWRP can't flash OTA's anyway, so don't try that again either. I'd strongly recommend not using a toolkit to flash the factory images too. I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Snakielols1984 said:
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Click to expand...
Click to collapse
Can fastboot see your device when you're in bootloader?
Yes fastboot is able to reconize my device.
Snakielols1984 said:
Yes fastboot is able to reconize my device.
Click to expand...
Click to collapse
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
I've actually tried flashing stock images but every time I tried to run fastboot command I get these errors, "command not found" and I believe the other erro is "file path not found". There's another error that I can't remember off the top of my head what it. When I get home I'll try to run the commands again and see what errors I get
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
elfrosto said:
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
Click to expand...
Click to collapse
on another note I have not flashed Android N OTA. I downloaded that and install via OTA.
wrong thread
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Snakielols1984 said:
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Click to expand...
Click to collapse
What bootloader version are you on currently? Although updated bootloader is recommend, you should be able to skip this step without any issues.
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Snakielols1984 said:
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Click to expand...
Click to collapse
Please post the entire command you are using, as written in your terminal prompt. "No command" sounds like an unrecognized command is being issued. We must use ./ in addition to the fastboot or adb command in order for OSX to execute the action. If following Heisenberg's guide for fastboot, the lone change you need to make for OSX is:
./fastboot devices
./fastboot flash
./fastboot reboot
./ADB devices
Try this out and post your results.
Sent from my Nexus 5X using Tapatalk
Just throwing this out there, it is possible to flash an OTA in TWRP. You still need a PC but its do-able.... I flashed Android N Final to my 6P yesterday by copying the OTA zip (uploaded thanks to another member) to SD, Wiped device as I normally would with any other ROM (left SD intact obviously), Flashed OTA ZIP, rebooted straight to bootloader after flash, fastboot erase boot, fastboot erase recovery, fastboot flashed DECRYPTED BOOT.img (which can be found easily), fastboot flashed TWRP 3.0.2-1 (version just released for N), fastboot format userdata, fastboot format cache, reboot from bootloader directly into TWRP, flashed superSU 2.74, reboot system..... Phone runs beautifully. Not a single issue. Entire process from start to finish was less than 10 minutes.
Its not the most practical route but it does indeed work. OTA just hes to contain the entire Image. I should also mention that this was a jump from a Marshmallow based rom (RR) so you don't have to be on an N preview in order to do this....
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Am in the same situation. Waiting to hear back from Cameron Yan.
Looks like you might need to flash the 1.5 version via fastboot and go through each update iteration.
Yeah u might have to flash 1.5
Your Jide Ambassador is here!!!
---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------
U can't just remove the rooting and think the update will be applied. Each updated is like a layered cake placed on its foundation. When you rooted you messed with pliers of stability for future layered updates and the updates check where they are suppose to be place. If something is missing or out of place you are going to get an error.
Your Jide Ambassador is here!!!
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
I had the same experience and ended up flashing 1.5 and then going through the automatic updates. Took a little while, but the update installed and I am back to stock for the time being.
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Same issue for me I am scared about the root by King root : not the cleaner tool ...
iceheart3131 said:
Same issue for me I am scared about the root by King root : not the cleaner tool ...
Click to expand...
Click to collapse
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
tomlogan1 said:
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
Click to expand...
Click to collapse
Ok , but where can I found this 1.5 version please ? there is no Download section on Jide webpage ...
Ok 1.5 version and toutos available on JIDE webpage
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
iceheart3131 said:
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
Click to expand...
Click to collapse
Probably obvious, but to you have USB debugging enabled?
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
iceheart3131 said:
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
Click to expand...
Click to collapse
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in order for this to work. Worth a try.
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
iceheart3131 said:
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
When I use adb I get the device SN. When I use fastboot devices I get nothing. If I then adb reboot bootloader I get the attached response.
Click to expand...
Click to collapse
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
To flash the ROM, please download the file from the following link and follow the below instructions.
https://drive.google.com/open?id=0B...1FVVR3RkRya29sakQ3SEdVbXU5cUg0YTIzUnNfUTRWMTA
Installing image files using fastboot
1. Make sure your Remix has working fastboot (http://wiki.cyanogenmod.org/w/Fastboot) and adb (http://wiki.cyanogenmod.org/w/Adb).
2. Download images
The information of the image zip file:
Images Zip File Name: SK1WG.zip
md5: f993e49ff5f0bfac169dcb62b2e820e8
sha1: 6f9b364f46680ff1294ff2eb9e3fe9aba6592d5a
3. Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
5. Make sure the fastboot binary is in your PATH (http://wiki.cyanogenmod.org/w/Doc:_paths) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot (http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro) documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV (http://wiki.cyanogenmod.org/w/UDEV) rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
Click to expand...
Click to collapse
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
iceheart3131 said:
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
Click to expand...
Click to collapse
Maybe a driver from previous devices? I'm using the Android naked drivers and they work with the tablet as well as my Android phone.
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
iceheart3131 said:
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
Click to expand...
Click to collapse
Congratulations! Now you can be ready when custom ROMs become available. Your presistance paid off.
Hi there!
I'm newby with android and unlocking the device. My device ZTE Axon 7 A2017G
I want a device running on Lineage os. So I try since 3 days to backup and flash the recovery with axon7tool.
I get always the error message: failed to connect.
I try to install the driver with zadig and now i see the Q...BULK device but still become this error...
I was on android 7.1 B01 and now have downgraded to android 6.0.1 (A2017GV1.0.0B10)
Still the same error.
I changed the computer, still this stupid error.
Can anybody help me, I'm frustrated...
I had this issue and solved it by showing all file extensions in windows. When you rename the recovery.img to recovery.bin you have to make sure that it's actually an BIN file and so you need to have show all file extensions on in the windows settings.
thanks for your answer.
I'm realy shure that I have activated this option, because of other development stuff
Even the first command in each tutorial is not working: "axon7tool -r gpt boot recovery"
When I disconnect my axon and then run the command again I become this error: "Device not connected/found, Failed to connect"
So this means, if I connect the device and I see only the error: "Failed to connect"
the axon7tool see my device but can't connect to them?
p.s. after the downgrad from android 7.1 to 6.0.1 I don't see any updates such as android 7 and I haven't a connection to mobile data (3G/4G). Very frustrated when I want to use whatsapp outdoor
Sorry. I don't know what your issue is then. I'm sure someone else here can help you.
Do you have then Qualcomm drivers installed? If not, try this: QUD.WIN.1.1 Installer-10039.2.zip
If it's still not detected, use the Zadig Tool found here
I had a similar issue. You have to grant admin rights when opening a command window.
Send from ZTE A2017G using Tapatalk
KwesiJnr said:
Do you have then Qualcomm drivers installed? If not, try this:
If it's still not detected, use the Zadig Tool found
Click to expand...
Click to collapse
thank you. What should I select in the wizard when he ask me for the following:
Please choose between WWAN(NDIS6.20) and ETHERNET(NDIS 5.1)
- WWAN-DHCIP is not used to get IPAddress
- ETHNER-DHCP is used to get IPAddress
First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.
KwesiJnr said:
First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.
Click to expand...
Click to collapse
oh wow! One step further.
The tool waits a second an then I see this error:
C:\Users\bearbeer\Downloads\adb>axon7tool -r boot
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
I dont understand the message.
bearbeer said:
oh wow! One step further.
The tool waits a second an then I see this error:
I dont understand the message.
Click to expand...
Click to collapse
Good, reboot your device into EDL mode once more and try again.
KwesiJnr said:
Good, reboot your device into EDL mode once more and try again.
Click to expand...
Click to collapse
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?
bearbeer said:
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?
Click to expand...
Click to collapse
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.
KwesiJnr said:
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.
Click to expand...
Click to collapse
thanks again. It works!
What's the next step to become lineageos running on my device? Download and install lineageos or do I need something else before?
If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.
KwesiJnr said:
If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.
Click to expand...
Click to collapse
Ok I have flashed the TWRP Recovery (not the latest because the latest boot not up) and unlocked the bootloader. What's the Nougat Bootstack and how do I install it?
Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.
KwesiJnr said:
Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.
Click to expand...
Click to collapse
What's the best way to upgrade the twrp?
bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.
bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
0. Reboot to TWRP, then copy the desired Recovery Image file you want to upgrade to, (e.g. twrp-3.1.0.0-ailsa_ii.img) to your Internal Storage.
1. Tap Install Image from the lower right corner. Proceed to select the recovery image you just copied to your device.
2. You should now see a radio list. Select Recovery, then swipe to flash.
3. Reboot.
That is all.
Alternatively, you can flash the recovery upgrade file via fastboot, like you did the older version. Just make sure you flash the older version first, THEN the newer. Should work like a charm.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
metpolds said:
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.
Click to expand...
Click to collapse
Lmao. I feel you, bro. Pretty convinced he's new to these forums as you guessed, and I'm sure he likely doesn't know about the 'Thanks' system. You know, benefit of the doubt and all.
Ultimately, I just wanted to help out. I know how frustrating it can be with these things so...
Thank you! Ok I'm now on "twrp-3.1.0-0-ailsa_ii.img" and it works.
Yes this is correct. I don't saw the "thanks" button...
I'm so happy that all of you help me. As a newby there are so many threads, tuts, ... an everywhere all goes right. But on my device nothing works at first try. Thank you a lot! :good: :laugh:
So I am really stuck and don't know what to do. Unlocked the bootloader, installed twrp just fine and rooted. then I went to install a custom rom after I made sure it was working and then it kicks me back to the normal recovery. twrp is gone and I can't fastboot the firmware cause I wiped it to flash a rom. Now when I go to adb sideload I keep getting error 21 footer is wrong and signature verification has failed. Can someone please point me in the right direction to fix my phone? thanks
Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds
gm007 said:
Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.
tommyjames1992 said:
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.
Click to expand...
Click to collapse
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.
gm007 said:
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.
Click to expand...
Click to collapse
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.
tommyjames1992 said:
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.
Click to expand...
Click to collapse
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.
gm007 said:
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.
Click to expand...
Click to collapse
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.
tommyjames1992 said:
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.
Click to expand...
Click to collapse
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948
gm007 said:
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948
Click to expand...
Click to collapse
So I am still got getting fastboot working to flash stock firmware but I managed to reflash twrp and install AICP custom rom. So at least I can use the device. I will figure out the fastboot stuff later I guess lol.
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