Related
I want to update radio and clockwork mod recovery but I can't flash image files. I tried two ways the below one being the first:
"1. Extract the contents of the radio zip package. You should have radio.img file in it.
2. Copy/move the radio.img file to “Tools” directory of the Android SDK setup. Fastboot.exe will also be located in the same folder.
3. Connect the Phone to computer via USB cable.
5. Open the command prompt and run the following command:
adb reboot bootloader
fastboot flash radio radio.img
6. Wait for the radio flash to complete.
After flashing is completed, reboot your Android phone. It should boot with the new Radio ROM! That’s it. You have successfully installed Radio.img on your Android Phone."
I couldn't run the fastboot command. After reboot to bootloader I couldn't connect to the desire. All I got was an error message saying "device not found". What's up with that? I do have the right drivers (at least i think so). Before the reboot the device was found all right. I rebooted via the command prompt and it worked just fine. USB debugging was activated all the time.
The second method I tried was using android terminal (trying to flash the new recovery) like this:
su
flash_image recovery /sdcard/recovery.img
The super user command worked fine but the next one didn't. Another error message "flash_image not found"
This has nothing to do with the recovery image not being in the right place or me misspelling. Tried it many times belive me. What seems to be the case is that I don't have flash_image on my phone.
Am I missing something here. I'm new to rooting and installing ROMs so I figure I might
Background:
I just recently rooted my Desire. I wanted more space for apps and to get rid of many apps included in the stock ROM.
I searched all over the place and figured Redux to be the ROM for me. I used the unrevoked method too root and Alpharev 1.8 to S-off. I use the Oxygen HBOOT flashed via the zip-file from Alpharev. I don't think I've ever used adb to flash images since I never had to.
Any ideas?
1. Install the HBOOT drivers form unrevoked site (From here.)
2. Download android SDK from their site and install it + platform tools, revision 3 (from SDK MANAGER).
3. Reboot the phone into fastboot (POWER + BACK key). Should say FASTBOOT USB.
4. Run CMD.EXE and navigate to your folder where is fastboot.exe is located (android-sdk-\tools) on your hard drive.
5. run command (e.g. fastboot flash radio xyz.img)
6. run command reboot-bootloader
Sorry, for the noobish instructions, but this should work, I just did it yesterday.
Don't worry, I'm a noob
I have already done 1 and 2. All drivers are up to date. I do get to FASTBOOT USB when doing 3 but then I can't execute any adb commands due to my device not being found.
Weirdly I can see Android Phone 1 on my laptop where you unmount en externel drive.
I might just do steps 1 and 2 over again.
For now I managed flashing the new Clockwork Mod Recovery using a guide suggesting to download a flash_image file extracted from one of the cyanogenmod ROMs and pushing it to the system/bin directory on the phone. adb commands works fine when the phone is completely rebooted so I could do that. Then I just used Terminal Emulator to flash the recovery image.
Thanks for your instructions!
Hi there.
As the above title says, what happen if I do so?
I do not have recovery version 2.5.1.3 in my ROM Manager anymore(I have no idea know why). Also do not have 3.0.2.5.
The only recovery I have is 2.5.1.4, 3.0.0.5, 3.0.0.6 and 3.0.2.4. Plus I am unable to flash 2.5.1.4 version(it pops up an error)
Some have no issues, but some have experienced issues when trying to restore cwm backups.
Have a look in the LeeDrOiD 2.2.3 thread a few days ago. I have posted methods to manually flash it via a tool or adb commands. I have also provided dl links as well.
Sent from my Desire HD using XDA App
Hi Upintheair
Thanks for the reply. Erm.. do you remember the exact date you post that in LeeDroid's thread? The thread is overloading. I cannot find them. =(
From Index of /cm/recoveries Download recovery-clockwork-2.5.1.3-ace.img
Try one of these 2 tools, instructions are on the threads;
1. Thread: [TOOL][All devices & OS] Fastboot Commander [v.1.1]
Download: Fastboot Commander v1.1
2. Thread: Android Flasher
Download: [UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.7.4]
OR
Manually through ADB:
1. Place the image in where fastboot.exe is located.
2. Connect phone to PC with Bootloader FASTBOOT USB
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
Click to expand...
Click to collapse
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
kgulruh said:
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
Click to expand...
Click to collapse
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash . Also ensure notebook & phone batteries have near full charge.
Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.
...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux
Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)
To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.
If you want to use CMD:
Place image inside SDK folder where fastboot & adb.exe are located.
Rename it to radio.img (unless you like to type the whole name again)
CMD type: " fastboot flash radio radio.img", then
"fastboot reboot"
I am not too sure about Linux PCs, always been Windows until Android.
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
SERGI.3210 said:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
Click to expand...
Click to collapse
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Thanks UpInTheAir
I'll try it later tonight. Guess I will try to manually flash them.
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
I just recalled I read it somewhere last time when I was learning how to flash new radio. x)
superstick1 said:
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
Click to expand...
Click to collapse
If you are referring to the "tool" as in the CMD (Command Prompt)?
If this is what you mean, the answer is Yes & Yes.
Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
superstick1 said:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
Click to expand...
Click to collapse
Ensure Fastboot is OFF & USB debugging ON in phone settings
When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
Did you test Fastboot communication by command "fastboot devices"?
Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
superstick1 said:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
Click to expand...
Click to collapse
1. Mine works fine with usb debugging on & fastboot off.
2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.
3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"
If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
Sent from my Desire HD using XDA App
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
UpInTheAir said:
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Click to expand...
Click to collapse
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.
Certainly .... which is the meaning of "koush"???
superstick1 said:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
Click to expand...
Click to collapse
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.
3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.
Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8
I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.
View attachment Recovery_Ace_v2.5.1.3.zip
View attachment Recovery_Ace_v3.0.2.8.zip
Installation:
1. Power off your DHD
2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.
3. Plug-in the USB cable. (FASTBOOT USB)
4. Extract xxxx.zip
5. Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
6. Done! The device will be automatically rebooted.
7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.
I tested the windows commands and worked perfect Linux should too!!
I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
UpInTheAir said:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Click to expand...
Click to collapse
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.
For me typing in linux is better then knowing nothing in windows
superstick1 said:
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
Click to expand...
Click to collapse
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).
Try that way.
I have rooted my device using towel root which doesn't unlock the boot loader. I then used the twrp manager to install custom recovery. I am wondering how to restore everything back to factory as all the tutorials I have seen so far require an unlocked boot loader. Any help will be appreciated, thank you.
Flash a stock r for your phone
swagg blasted from TMO LG G3
jailbreakkid23 said:
Flash a stock r for your phone
swagg blasted from TMO LG G3
Click to expand...
Click to collapse
If I download a stock image from google and flash it from my nexus 7 using twrp will everything be restored to factory settings?
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
fastboot
Jordydaman said:
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
Click to expand...
Click to collapse
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
@SidDev said:
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
Click to expand...
Click to collapse
Would you mind finding a link for me ? I have never encountered this before as I have always unlocked the bootloader to root but this time I used towel root which was different as explained above.
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
try this and press thanks
Jordydaman said:
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
Click to expand...
Click to collapse
nope,
Step 1: Download the ADB/Fastboot files and the
USB drivers for Windows based PC first. The the
latest factory image for your Nexus device can be
downloaded directly from Google’s website .
ADB/Fastboot – Mac , Windows
USB drivers for Windows
Extract the contents of the ADB/Fastboot ZIP file
inside a new folder called ‘google’ on your desktop.
Extract and transfer the contents of the factory
image inside this folder as well. The list of files will
include a ZIP file containing the codename of your
Android device, two files with “flash-all” names, and
a bootloader image file. All the extracted contents of
the factory image should be inside the same folder
as the ADB and Fastboot file, otherwise you will get
a file not found error.
Make sure to install the ADB drivers as well if you
are running a Windows based PC.
Step 2: Now, reboot your Nexus device in bootloader
mode. This is usually done by switching off the
device, and pressing the Volume down + Volume Up
+ Power button simultaneously. If that does not
work, try the Volume down + Power button
combination.
After the device has booted into bootloader mode,
connect it to your PC.
Step 3: Open a new Terminal or Command Prompt
window, and navigate to the ‘google’ folder that you
created in Step 1. Before we start flashing the
factory image, we need to make sure that your
Nexus device is being detected by the PC.
fastboot devices
If you are using a Mac, then you need to prefix a “./”
before every Fastboot command. So, the above
command will look something like this on a Mac -:
./fastboot devices
The above command should confirm if your device is
indeed being detected by your PC or not. If it is,
then proceed to the steps below. If not, repeat the
steps above again. Make sure that you have properly
installed the drivers and are inside the correct
folder.
If you are running Windows, copy-paste the following
command in the command prompt window -:
flash-all.bat
On a Mac, copy-paste the following command -:
./flash-all.sh
The script will then automatically flash the full
factory image on your Nexus device. Once the
factory image has been flashed, your device will
automatically reboot. Keep in mind that the first boot
might take some time so please be patient.
If the flash-all.sh script gives you a fastboot not
found error on your Mac, open up the file in Text Edit
and add a “./” before every fastboot command.
The flash-all script included in the factory image
might not work for all. It has always been pretty
unreliable and has only worked once for me in the
last 2 years. If you are in the same boat as me, you
will have to flash each partition manually on your
device. This is slightly cumbersome though.
The command to manually flash a partition via
fastboot is “fastboot flash partition filename.img”. In
the factory image that you extracted in Step 1, you
will notice there is another ZIP file. Extract the
contents of that ZIP file inside the ‘google’ folder.
Now, its time to manually flash the partitions to your
Nexus device. We will first begin with the bootloader.
fastboot flash bootloader filename.img
Then, we will flash all other partitions. They don’t
necessarily need to be in the same order as I have
listed them below. The names of the image files in
the factory image will clearly indicate the partition
they are intended for as well.
fastboot flash boot filename.img
fastboot flash radio filename.img
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
Thank you very much I will try this today.
I couldn't flash all and when I flashed the bootloader it came up with failed bootloader is locked?
Enter this command to unlock the bootloader:
fastboot oem unlock
After unlocking, you can run flash-all.bat (or run manual fastboot commands to flash).
Any help would be appreciated. This is my first time dealing with Magisk, I've always used SuperSU in the past. I finally used my unlock code and the bootloader says unlocked, that was easy. I installed the Magisk Manager apk but am having trouble with Magisk itself. I'm used to flashing in TWRP, which I apparently can't install until Magisk is installed. I have two options, install - download zip only, and patch boot image file...
So I was trying to use the boot image file from this thread https://forum.xda-developers.com/mate-20-x/development/guide-mate-20-x-root-t3883269 and either patch it or used the patched one, but when my phone goes into the bootloader screen, adb is not recognizing the phone or finding the file which I set inside the adb folder itself. Sorry, I am not a noob to flashing. Done many many phones rooting, unlocking, roms, modems, etc. I am just new to adb and Magisk. Any help would be great as I've been at this all day reading and downloading things I needed. Thank you.
EDIT: I'm not sure if I'm putting the .img file in the wrong folder??? I am stuck on step 5 in that thread.
So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory
DavidMT909 said:
So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory
Click to expand...
Click to collapse
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'
lightning413 said:
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'
Click to expand...
Click to collapse
Thank you, but I may have messed up my phone now. I was trying this from the thread above, and even his example shows Magisk in it.
Step 5:
-Once the device is in bootloader and connected to the PC, run the command "fastboot flash recovery_ramdisk recovery_ramdiskMagiskVARIANT" with VARIANT being whatever ramdisk you downloaded. For example with AL00 you would input "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00.img"
As soon as I tried your way it seemed to work... except when I booted it still did not have root. And now I cannot get into fastboot or recovery. It just keeps rebooting to the phone if I try recovery or fastboot. I used to be able to do this stuff following directions. It just doesn't seem to be working out. Thanks for trying.
My devices still lists in adb, but not fastboot. I'm still working on this. I do make an effort to do things myself.
Okay, I don't know what happened. My Magisk had an update, I installed it and rebooted and for the first time two green checks in Magisk, ran root checker and I have root. So hopefully I can install TWRP now and on to the ROM. Slow progress...
I have TWRP. Time to make a backup, and I'll install a ROM next.
Hello all together,
I recently have the problem that the fastboot boot "img" command gives me the error: FAILED (remote: 'Unrecognized command boot').
I had updated to Magisk 26.0 last week and later to 26.1. Unfortunately, Comdirect with Magisk 26 recognizes the root and refuses the service. So I wanted to downgrade again to Magisk 25.2.
I downloaded the patched 25.2boot.img from here https://forum.xda-developers.com/t/...oos-13-f21-f75.4252373/page-109#post-88329359.
The 9Pro is recognized in Windows 11. ADB devices command recognizes it as well. Also the command fastboot devices is executed and shows the 9Pro as detected.
If I now try to boot the boot.img it is successfully copied but aborted with the error "FAILED (remote: 'Unrecognized command boot')".
The same happens via Live LinuxMint and via rootTerminal.
Boot.img is successfully copied but aborted with the same error.
This is really strange because 3 weeks ago I switched to A13 and successfully patched the Boot.img.
Also I had not installed/uninstalled or changed any programs, drivers or anything else on my pc in that time.
I have also tried all USB ports and different cables, all without success.
Use the cmd not the power shell and open the cmd from adb platfrom tools folder
Dan3ll1 said:
Hello all together,
I recently have the problem that the fastboot boot "img" command gives me the error: FAILED (remote: 'Unrecognized command boot').
I had updated to Magisk 26.0 last week and later to 26.1. Unfortunately, Comdirect with Magisk 26 recognizes the root and refuses the service. So I wanted to downgrade again to Magisk 25.2.
I downloaded the patched 25.2boot.img from here https://forum.xda-developers.com/t/...oos-13-f21-f75.4252373/page-109#post-88329359.
The 9Pro is recognized in Windows 11. ADB devices command recognizes it as well. Also the command fastboot devices is executed and shows the 9Pro as detected.
If I now try to boot the boot.img it is successfully copied but aborted with the error "FAILED (remote: 'Unrecognized command boot')".
The same happens via Live LinuxMint and via rootTerminal.
Boot.img is successfully copied but aborted with the same error.
This is really strange because 3 weeks ago I switched to A13 and successfully patched the Boot.img.
Also I had not installed/uninstalled or changed any programs, drivers or anything else on my pc in that time.
I have also tried all USB ports and different cables, all without success.
Click to expand...
Click to collapse
ChrisFeiveel84 said:
Use the cmd not the power shell and open the cmd from adb platfrom tools folder
Click to expand...
Click to collapse
Same result.
Dan3ll1 said:
Same result.
Click to expand...
Click to collapse
You use the last platfrom tools.v34?
Yes, everything is up to date. I just cant figure out why all of a sudden it stopped working...
What for fastboot driver Have you installed ?
I use the minimal adb and fastboot drivers from here (XDA).
Dan3ll1 said:
I use the minimal adb and fastboot drivers from here (XDA).
Click to expand...
Click to collapse
Minimal adb is to old
Then what is the way to go?
Dan3ll1 said:
Then what is the way to go?
Click to expand...
Click to collapse
Update the android platfrom tools
Like i said. They are the newest i use.
From here https://developer.android.com/tools/releases/platform-tools
Using the latest OnePlus USB drivers with " disable signed drivers" for windows? And I would change the 25.2boot.img to just boot.img. the extra period may be causing an issue...just my thoughts.
If you want change kernel you have to flash it via "fastboot flash boot magisk.img". You cannot directly boot other kernel with "fastboot boot magisk.img". This command is used for booting recovery without flashing it.
I dont want to flash a kernel. I want to boot temp root with the patched magisk image and then flash it via magisk.
Bugscze said:
If you want change kernel you have to flash it via "fastboot flash boot magisk.img". You cannot directly boot other kernel with "fastboot boot magisk.img". This command is used for booting recovery without flashing it.
Click to expand...
Click to collapse
And you can boot other kernel with fastboot boot (when the Other kernel is a full img)
When this is your boot.img than you can it flash direct no need boot this image
Dan3ll1 said:
I dont want to flash a kernel. I want to boot temp root with the patched magisk image and then flash it via magisk.
Click to expand...
Click to collapse
I mean i could. But like all the tutorials and how to guides say that booting temp root and flashing it with magisk is the safest way.
And it did it this way like a million times before. And now i get this strange error that i dont understand why it is happening.
Edit:
The fastboot flash command works just perfectly fine. But not the fastboot boot command?