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.
Related
Have completed rumrunner root for htc one.
Have installed twrp through adb using command prompt.
Then when trying to reboot system it boots up in recovery.
Need help to find out how to get back on my phone.
Have found similar sites with information but not clear enough for me to understand
I'm able to access twrp so i would assume it's a mount of the sd card but i am not seeing that option anywhere
twrp v 2.6.3.0
I know it's late guys thanks for your help!
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img.
Click to expand...
Click to collapse
Either the tutorial was completely written wrong, or you read them wrong. There's no way of telling which happened, but the point is to be very careful with fastboot.
The command "fastboot flash boot file.img" doesn't flash recovery in your boot partition unless you mis-labeled your .img file and flashed the wrong file in the wrong place.
Most people modding their phones are going to be using fasboot to flash to boot, recovery, system, or bootloader. It's important to understand all of the places that fastboot can flash before you start pushing in .img files. Understanding fastboot commands can also help you possibly identify if someone made a typo in their guides.
Want to put in recovery? "fastboot flash recovery recovery.img". Want to put in a new kernel? "fastboot flash boot boot.img", and so on. Ensure that you've got files that are properly named and you won't ever have to worry about flashing the wrong thing in the wrong place.
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
Click to expand...
Click to collapse
Jjust understand what you're flashing, you can't 100% trust a tutorial..
If you do the command, fastboot flash boot boot.img, you BEST DAMN be sure that is a kernel/boot.img you are flashing and make sure your working is right, if you fastboot flash a boot.img to say recovery.img, you are screwed.
make sure the file is right my MD5, also make sure the tutorial is good, messing with ANYTHING in fastboot is dangerous.
I know that I have to temporarily fastboot boot into twrp. so when i type fastboot boot path/to/twrp.img it says there is no such file or directory! i tried it so many times. i want to root my phone. I easily unlocked the bootloader, but i cant boot into the twrp. the file clearly exists ... and yes, i opened the command prompt in the folder containing both the twrp.img and fastboot.exe. i'm perplexed.. and infuriated! this was supposed to be a easy process. i googled my issue. nothing to be found or that even makes sense. can someone help me? I would appreciate it so so so so much.
Abbieru said:
I know that I have to temporarily fastboot boot into twrp. so when i type fastboot boot path/to/twrp.img it says there is no such file or directory! i tried it so many times. i want to root my phone. I easily unlocked the bootloader, but i cant boot into the twrp. the file clearly exists ... and yes, i opened the command prompt in the folder containing both the twrp.img and fastboot.exe. i'm perplexed.. and infuriated! this was supposed to be a easy process. i googled my issue. nothing to be found or that even makes sense. can someone help me? I would appreciate it so so so so much.
Click to expand...
Click to collapse
If they are in the same folder you don't need the path. Probably getting messed up with spaces or something on the path.
Rename the TWRP file to TWRP.img
Fastboot boot TWRP.img
Abbieru said:
I know that I have to temporarily fastboot boot into twrp. so when i type fastboot boot path/to/twrp.img it says there is no such file or directory! i tried it so many times. i want to root my phone. I easily unlocked the bootloader, but i cant boot into the twrp. the file clearly exists ... and yes, i opened the command prompt in the folder containing both the twrp.img and fastboot.exe. i'm perplexed.. and infuriated! this was supposed to be a easy process. i googled my issue. nothing to be found or that even makes sense. can someone help me? I would appreciate it so so so so much.
Click to expand...
Click to collapse
If you are using Windows 10 even after u rename it try fastboot boot TWRP.img.img. For some reason u have to add extra IMG. I saw someone posted that somewhere after lots of screwing around. What worked for me anyways
Make sure your SDK is up-to-date and flashing TWRP RC1
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be
Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.
HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #
Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.
I have the latest driver's installed.
I have tried multiple adb drivers and multiple windows 10 computers with no luck
I have downloaded latest firmware. I extracted it. I got the boot img. I loaded it on my phone.
I patched it with magisk.
When I open up cmd promo and type fastboot devices I'm given an id
But when I go to flash the boot img cmd says partion not there. Can someone please help?
Jmcarls20 said:
I have the latest driver's installed.
I have tried multiple adb drivers and multiple windows 10 computers with no luck
I have downloaded latest firmware. I extracted it. I got the boot img. I loaded it on my phone.
I patched it with magisk.
When I open up cmd promo and type fastboot devices I'm given an id
But when I go to flash the boot img cmd says partion not there. Can someone please help?
Click to expand...
Click to collapse
I patched it with magisk. , This file need to be in adb folder .
Are you trying to adb sideliad or fastboot it?
Personally i would use the following command:
Fastboot flash boot magisk_patched.img
This of course assumes a few things:
1) that you have put the phone in bootloader mode
2) that you are connected via usb cable to a pc
3) that the adb devices command shows your device
4) that you didn't rename the patched boot image file magisk created for you
5) that the fastboot, adb and patched magisk file are all in the same location and that you issued that command from that same location.
Not trying to ignore the topic of this thread, but shouldn't this be under discussions? It's currently under ROMs and Kernels and Development, which is reserved for new projects rather than questions about rooting..
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?