Related
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
It means you've not copied the files into your ADB folder as it can't find the fastboot files
ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
gamer.11 said:
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
Click to expand...
Click to collapse
This won't work if fastboot binary isn't in env PATH.
EddyOS said:
It means you've not copied the files into your ADB folder as it can't find the fastboot files
Click to expand...
Click to collapse
"Into your FASTBOOT folder". adb's got nothing to do with this.
http://forum.xda-developers.com/showthread.php?t=2513701
Follow method two in this guide.
beekay201 said:
This won't work if fastboot binary isn't in env PATH.
Click to expand...
Click to collapse
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Easiest way is to extract the sh1t out of the Google file until you eventually see all the img files. Then extract the fastboot zip into the same folder they're in and open a command prompt there.
Fastboot zip -
https://www.dropbox.com/s/b8wxmwfi2ekdw3a/Adb And Fastboot.zip?dl=0
Sent from my Android 5.0 Nexus 5
gamer.11 said:
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Click to expand...
Click to collapse
Because it's in your PATH.
beekay201 said:
This won't work if fastboot binary isn't in env PATH.
"Into your FASTBOOT folder". adb's got nothing to do with this.
Click to expand...
Click to collapse
People refer to the folder with ADB and fastboot in it as the ADB folder (If you had adb/fastboot in the system path this wouldn't even be required)
Do you really think I meant them to use ADB? Come on, now
beekay201 said:
Because it's in your PATH.
Click to expand...
Click to collapse
oh "env" meant environment, sorry did not understand your shot hand.
by the way OP? solved your issue?
EddyOS said:
People refer to the folder with ADB and fastboot in it as the ADB folder
Click to expand...
Click to collapse
I refer to this folder as the platform tools folder
nikon120 said:
I refer to this folder as the platform tools folder
Click to expand...
Click to collapse
Makes more sense I guess, just more to type! This is where being in PATH makes life better
Hello!
I'm stuck trying to flash TWRP into my devices and hoping now to maybe get some help figuring this out.
My devices is
LG Nexus 5, D821, Android 6.0.1
OnePlus 3T, A3003, OxygenOS 5.0, Android 8.0.0
I wanting to flah them both with TWRP Recovery, I've followed the tutorials for each phone from the links below
LG Nexus 5
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
OnePlus 3T
http://www.teamandroid.com/2017/02/24/install-oneplus-3t-twrp-3-0-3-recovery-complete-guide/2/
I have installed the android studio for my PC and downloaded the neccesary tools to make this work as "Android SDK Platform-Tools", "Android SDK Tools", "Google USB Driver". I have unlocked the bootloader on both phones and downloaded the latest TWRP.img file for each phone from
LG Nexus 5
https://eu.dl.twrp.me/hammerhead/
OnePlus 3T
https://eu.dl.twrp.me/oneplus3t/
I've located each file in the same directory as adb and fastboot. The problem for me now is when I'm in command prompt and typing the following command
"cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery recovery.img"
I get the following text
"error: cannot load 'recovery.img': No such file or directory"
I have tried to download older twrp files and also from other pages but the issue remians. And when I'm in windows and trying to open the .img file I get a window that says
"It is not possible to mount the file"
"The Disc Image file is corrupted"
How can I solve this issue? Please Help
I've located each file in the same directory as adb and fastboot.
Click to expand...
Click to collapse
You mean your recovery.img is placed in your platforms-tools folder?
If so, try providing the full path to the recovery image in your command, for example:
Code:
cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery Desktop/android-sdk-windows/platform-tools//recovery.img
Also, I believe you need to reboot into bootloader before flashing the recovery, if you aren't aware already.
unignostik said:
You mean your recovery.img is placed in your platforms-tools folder?
If so, try providing the full path to the recovery image in your command, for example:
Code:
cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery Desktop/android-sdk-windows/platform-tools//recovery.img
Also, I believe you need to reboot into bootloader before flashing the recovery, if you aren't aware already.
Click to expand...
Click to collapse
Thank you! It worked now
EmmanouilEk said:
Thank you! It worked now
Click to expand...
Click to collapse
good stuff :good:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Thanks dear I'm on 18.0830.2101.75 can you provide patched image boot for my version because i want to change fingerprint to WW then install newer version through my phone.
İs there stock boot.img
How to relock the bootloader and remove root?
M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Hey i got update version 18.0810.2101.95
Can i use this img to root or i have to update first?
Eeveeone said:
Hey i got update version 18.0810.2101.95
Can i use this img to root or i have to update first?
Click to expand...
Click to collapse
First update, then flash this img, this img caused bootloop my phone so take care.
sorankira said:
First update, then flash this img, this img caused bootloop my phone so take care.
Click to expand...
Click to collapse
If like that better not update to 18.0830. but how i want to get stock img for 18.0810
Eeveeone said:
If like that better not update to 18.0830. but how i want to get stock img for 18.0810
Click to expand...
Click to collapse
Download 18.0810 firmware on your PC and download dumper tool it will extract payload.bin you can find stock images there.
sorankira said:
Download 18.0810 firmware on your PC and download dumper tool it will extract payload.bin you can find stock images there.
Click to expand...
Click to collapse
Can you help me by doing it. coz i couldnt do the proper way. it say syntax error
Eeveeone said:
Can you help me by doing it. coz i couldnt do the proper way. it say syntax error
Click to expand...
Click to collapse
My internet is very slow indeed like 100KB/s but i will try to download it and send you the stock img.
sorankira said:
My internet is very slow indeed like 100KB/s but i will try to download it and send you the stock img.
Click to expand...
Click to collapse
Thx a lot.. currently i managed to do it. Now i have the stock img
Does anyone tried applying an OTA update while rooted? Is it sufficient to restore stock boot image, apply update zip file and flash new patched boot image? I have not tried it yet, because there is no TWRP available and I want to backup my data before trying.
MarekPietrzak said:
Does anyone tried applying an OTA update while rooted? Is it sufficient to restore stock boot image, apply update zip file and flash new patched boot image? I have not tried it yet, because there is no TWRP available and I want to backup my data before trying.
Click to expand...
Click to collapse
Yes you can apply ota update.
When the OTA Update finishes don't reboot click later, then go to magisk install OTA to inactive slot.
THANK YOU! This file saved my phone. I installed some other boot image that wouldn't let me boot the phone, this file brought it back to life.
Thank you again!
M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Hallo
Any boot.img for latest version WW ASUS-18.0840.2103.26-1.1.81?
Can`t get my payload working, because not installing in correct folder.
ltth said:
Hallo
Any boot.img for latest version WW ASUS-18.0840.2103.26-1.1.81?
Can`t get my payload working, because not installing in correct folder.
Click to expand...
Click to collapse
Try extracting from your phone for payload.bin file. Or there is a "rooting my notes" discussion video in one of the post. You can see there
I have the payload bin file, but can`t extract in payload_dumper-master (not working correctly so I get the boot.img
ltth said:
I have the payload bin file, but can`t extract in payload_dumper-master (not working correctly so I get the boot.im
Click to expand...
Click to collapse
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...
forum.xda-developers.com
Use this link to extract the boot.img from payload.bin using your phone. Give a try. I also had issues extracting from pc. So did in my phone and worked.
jhosharath said:
Try extracting from your phone for payload.bin file. Or there is a "rooting my notes" discussion video in one of the post. You can see the
Click to expand...
Click to collapse
I found a Payload_Dumper wich worked very well, just have execute the scipt, then I got my boot.img
Thanks for your help!!
Hello there. I updated my Nubia Z20 global ROM to android 11. I lost Google services in the process.
So I install the necessary drivers on my PC and used minimal adb and fastboot to unlock bootloader on my phone. But my problem is that I can't install TWRP recovery on the phone itself.
I used the Twrp recovery for nubia z20.exe to get the phone into fastboot mode but I cannot proceed any further.
Once the phone enters into fastboot mode, the computer wont detect my phone anymore.
Please help
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot flash recovery twrp.img
SMcC2 said:
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot
Click to expand...
Click to collapse
Thanks so much. I will use 7zip to get the twrp.img file.
After that, what do I do next?
do I open minimal adb and fastboot then type the command "fastboot recovery twrp.img"?
Mr Sparks said:
Thanks so much. I will use 7zip to get the twrp.img file.
After that, what do I do next?
do I open minimal adb and fastboot then type the command "fastboot recovery twrp.img"?
Click to expand...
Click to collapse
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
SMcC2 said:
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
Click to expand...
Click to collapse
Been working a 12 hour shift all day. I will definitely do this when I close and then give you a feedback
SMcC2 said:
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Hello again. I tried to extract using 7zip but I couldn't get the .img file. It gave me an error message
Can you share the link you used to download TWRP and copy the error message you are getting?
SMcC2 said:
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
Click to expand...
Click to collapse
I found this image file. Is it the one?
https://forum.xda-developers.com/attachments/recovery-nubia-img.5368983/
Hello.
I have a DOOGEE S59 pro phone and i tried a bunch of times to unlock its bootloader, but it didn't work.
I've already done these things:
I've installed the USB driver and the MediaTek driver from https://gsmusbdriver.com/
I've enabled "OEM unlocking" and "USB debugging" in the developper options
I've ran the CMD prompt in the platform-tools folder (which is placed in the C: drive) and run this code:
PS C:\Program Files\platform-tools> adb devices
List of devices attached
S59PROEEA0000026105 device
PS C:\Program Files\platform-tools> adb reboot bootloader (now the phone shows " =>FASTBOOT mode . . . ")
PS C:\Program Files\platform-tools> adb devices
List of devices attached
(My phone isn't listed anymore)
PS C:\Program Files\platform-tools> fastboot oem unlock
< waiting for any device >
And this is it. I can't do anything else. When I hold the power button + the volume up key I can return to normal mode, but what can I do to unlock the bootloader? I wanted to root my phone and flash some magisk modules after that, but the situation is like I said. Can somebody help me?
Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.
.
xinthenoob said:
Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.
Click to expand...
Click to collapse
Thank you, I'll try that and I'll tell you if it works.
KakoFed said:
Thank you, I'll try that and I'll tell you if it works.
Click to expand...
Click to collapse
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt[
[/QUOTE]
Click to expand...
Click to collapse
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?
xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
I also tried to open a command prompt in the mtkclient folder itself, and it said that:
pip : The term 'pip' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s
pelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ pip install -r requirements.txt
+ ~~~
+ CategoryInfo : ObjectNotFound: (pip:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
Alright, I don't know what have I done, but it totally worked! Thank you so much!
KakoFed said:
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?
Click to expand...
Click to collapse
It should be somewhere also don't use PowerShell, it's weird sometimes
xinthenoob said:
It should be somewhere also don't use PowerShell, it's weird sometimes
Click to expand...
Click to collapse
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help
KakoFed said:
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help
Click to expand...
Click to collapse
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix
xinthenoob said:
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix
Click to expand...
Click to collapse
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?
KakoFed said:
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?
Click to expand...
Click to collapse
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Ok, thanks, I'll try everything of that later
.
xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Hi, I have a problem AGAIN. When I flashed the boot.patched file, it was almost ok, until I saw that my bluetooth and WiFi connections stoped working after the flash. There was this window opening again and again that the Bluetooth app still stops working. I had to flash the normal boot.img file for it to work.
How can I solve this problem? I still want to root my phone
xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me
KakoFed said:
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me
Click to expand...
Click to collapse
Sorry I caught the flu and was out for a while but I'm glad you found a way