kevg 14 Posted January 26, 2023 Share Posted January 26, 2023 I just got a new Pro1-X and I'm following the rooting with Magisk document: https://community.fxtec.com/topic/3690-pro1-x-rooting-with-magisk/ Everything works up to step 11 of the "Root Pro1-X via Magisk" section. I have magisk_patched-25200_HsxJg.img locally downloaded from step 10. Next, in step 11, I run adb reboot bootloader. It restarts to the attached image (IMG_20230125_213340_947.jpg). If I try to run fastboot flash boot magisk_patched-25200_HsxJg.img, I just get the following: $ fastboot flash boot magisk_patched-25200_HsxJg.img < waiting for any device > So then I tried scrolling to Recovery mode, and pressing power. That then restarts to the "No command" screen (IMG_20230125_213942_773.jpg). I get the same "waiting for any device" output if I try the fastboot flash command here. I found elsewhere that from this screen, I can hold the power button and press the volume up key and then release both and I see the Android recovery screen (IMG_20230125_214520_909.jpg). I get the same "waiting for any device" output if I try the fastboot flash command here. Then I scroll down to Enter fastboot and press power to enter that. But I get the same "waiting for any device" output if I try the fastboot flash command here. If I go back to recovery mode, and instead go to Apply update from ADB, I then see the following from adb devices, but I still can't run fastboot flash. $ adb devices List of devices attached 8ce396c8 sideload How do I run fastboot flash? Quote Link to post Share on other sites
EskeRahn 5,455 Posted January 26, 2023 Share Posted January 26, 2023 There is a difference between "Enter Fastboot" and "Reboot to boatloader". I'm pretty sure you want the second Quote Link to post Share on other sites
Casey 321 Posted January 26, 2023 Share Posted January 26, 2023 7 hours ago, kevg said: $ fastboot flash boot magisk_patched-25200_HsxJg.img < waiting for any device > If you're using a Windows computer, try installing the Qualcomm driver. It might be due to your computer is unable to recognise your Pro1-X under bootloader mode. I'd also suggest trying out a different USB-C cable. Quote Link to post Share on other sites
kevg 14 Posted January 26, 2023 Author Share Posted January 26, 2023 9 hours ago, EskeRahn said: There is a difference between "Enter Fastboot" and "Reboot to boatloader". I'm pretty sure you want the second Choosing reboot to bootloader just takes me back to the first screenshot. Do I choose something other than Recovery mode there? Quote Link to post Share on other sites
kevg 14 Posted January 26, 2023 Author Share Posted January 26, 2023 6 hours ago, Casey said: If you're using a Windows computer, try installing the Qualcomm driver. It might be due to your computer is unable to recognise your Pro1-X under bootloader mode. I'd also suggest trying out a different USB-C cable. I'm on Linux. Page 2 of the linked PDF suggests the instructions should work on macOS and Linux. I noticed another document ("Flashing Stock Android with QFIL") requires Windows, but I don't need to flash the stock OS; I just want to root with Magisk. One new thing I found is that when I'm on the second screenshot (No command), if I do adb devices, it shows unauthorized, so that's probably the problem: $ adb devices List of devices attached 8ce396c8 unauthorized How do I authorize the adb connection during recovery mode? In normal operating mode, I had to authorize and accept something on my phone. I tried with the root user on my laptop but that didn't help. I've tried multiple USB cables with the same results, including a brand new one which was the Amazon brand so I guess it should be likely not a problem. I'm connecting to a USB-2 port on my laptop (not through a hub). I have a Lenovo X270 and I'm running the latest Android Studio platform-tools; Fedora 37, Linux kernel 6.0.17. Quote Link to post Share on other sites
claude0001 1,337 Posted January 26, 2023 Share Posted January 26, 2023 (edited) fastboot is way more picky about the USB connection than adb. If @Casey's suggestions do not help: Various RaspberryPi's have been 100% reliable for me when it comes to flashing Pro1(X) -- I've never again used adb/fastboot from my PCs since I found that solution. Edited January 26, 2023 by claude0001 1 Quote Link to post Share on other sites
kevg 14 Posted January 26, 2023 Author Share Posted January 26, 2023 1 minute ago, claude0001 said: fastboot is way more picky about the USB connection than adb. If @Casey's suggestions do not help: Various RaspberryPi's have been 100% reliable for me whan it comes to flashing Pro1(X). I can buy a RaspberryPi, but are there some diagnostics I can run to help figure this issue out? Quote Link to post Share on other sites
claude0001 1,337 Posted January 26, 2023 Share Posted January 26, 2023 (edited) 10 minutes ago, kevg said: I have a Lenovo X270 I have an X250 and could never use fastboot from it (original Pro1, Linux also here). 8 minutes ago, kevg said: are there some diagnostics I can run to help figure this issue out Probably ... There all kinds of tips and tricks (use external hubs, remove unnecessary devices from the bus, ...) but it all feels a bit like doing a rain-dance and tossing salt over your shoulder ... All I can say is: Since I have set up adb/fastboot on that Raspi3 (others have reported RPi4 will also work inspite of different USB HW), I have never looked back. Edited January 26, 2023 by claude0001 1 Quote Link to post Share on other sites
kevg 14 Posted January 26, 2023 Author Share Posted January 26, 2023 (edited) 6 minutes ago, claude0001 said: I have an X250 and could never use fastboot from it (original Pro1). Probably ... There all kinds of tips and tricks (use external HUBs. remove unnecessary devices from the bus, ...) but it all feels a bit like doing a rain-dance and tossing salt over your shoulder ... All I can say is: Since I have set up adb/fastboot on that Raspi3 (others have reported RPi4 will also work inspite of different USB HW), I have never looked back. I've never bought a Raspberry Pi before. Do you think the "Raspberry Pi 3 A+ Computer Board" will work ($60 on Amazon)? Edited January 26, 2023 by kevg Spelling Quote Link to post Share on other sites
claude0001 1,337 Posted January 26, 2023 Share Posted January 26, 2023 (edited) 1 hour ago, kevg said: Do you think the "Raspberry Pi 3 A+ Computer Board I have always only used "B" models, which come with 4 USB ports and Ethernet in addition to WiFi. This of course doesn't mean that the A+ will not work for your purpose ... Edited January 26, 2023 by claude0001 1 Quote Link to post Share on other sites
MrPib 31 Posted January 26, 2023 Share Posted January 26, 2023 1 hour ago, claude0001 said: I have an X250 and could never use fastboot from it (original Pro1, Linux also here). Probably ... There all kinds of tips and tricks (use external hubs, remove unnecessary devices from the bus, ...) but it all feels a bit like doing a rain-dance and tossing salt over your shoulder ... All I can say is: Since I have set up adb/fastboot on that Raspi3 (others have reported RPi4 will also work inspite of different USB HW), I have never looked back. I can attest that a Pi4 works flawlessly so far for flashing for me. Just had to do: sudo apt-get install -y android-tools-adb android-tools-fastboot to install the tools needed. 2 1 Quote Link to post Share on other sites
claude0001 1,337 Posted January 26, 2023 Share Posted January 26, 2023 3 minutes ago, MrPib said: I can attest that a Pi4 works flawlessly so far for flashing for me. Just had to do: Thanks for testing the Pi4 in this respect. I do not have any of these and always worried its USB-3.0 parts might behave differently when compared to the older models' USB-2.0. Good to know this is not the case. I'm not sure which OS you use on your RPi, but since 'buster' the respective Debian packages are just called "adb" and "fastboot". I.e. in recent Raspberry Pi OS, one would rather do sudo apt install adb fastboot 1 Quote Link to post Share on other sites
Hook 3,015 Posted January 26, 2023 Share Posted January 26, 2023 Whereas with Manjaro on a Thinkpad x230, fastboot has always worked for me. Didn't need to install anything, fastboot and ADB tools were already there. Quote Link to post Share on other sites
MrPib 31 Posted January 26, 2023 Share Posted January 26, 2023 36 minutes ago, claude0001 said: Thanks for testing the Pi4 in this respect. I do not have any of these and always worried its USB-3.0 parts might behave differently when compared to the older models' USB-2.0. Good to know this is not the case. I'm not sure which OS you use on your RPi, but since 'buster' the respective Debian packages are just called "adb" and "fastboot". I.e. in recent Raspberry Pi OS, one would rather do sudo apt install adb fastboot I'm running "Raspbian GNU/Linux 10 (buster)" You're correct, your sudo command above would have done it. Quote Link to post Share on other sites
kevg 14 Posted January 28, 2023 Author Share Posted January 28, 2023 (edited) I bought a Raspberry Pi 3 B and microSD, installed Raspbian, installed adb and fastboot, connected to phone (normal boot), authorized the Pi, ran adb reboot bootloader, entered recovery mode, phone goes to "No command" screen, but then I get a popup on my Raspberry Pi desktop that says: Unable to open MTP device "001,013" Clicked OK and ran adb devices, and I'm back to the "unauthorized" status and adb and fastboot don't work. Tried this in the Raspberry Pi as both a normal user and root (with adb kill-server in between). Tried with another USB C cable and got a similar error, although it ended with "001,016". Any ideas? Edited January 28, 2023 by kevg Quote Link to post Share on other sites
Hook 3,015 Posted January 28, 2023 Share Posted January 28, 2023 I'm a little confused by your descriptions. When you reboot to bootloader using adb, you should get the bootloader screen which is the same as your first screen shot way above except I think it says "START" in green at the top. I don't think it matters if you use the volume control to change what is at the top to "RECOVERY mode" because those are options you are scrolling through, but nothing changes unless you press power. That bootloader screen (with "START" or whatever at the top) is the bootloader. That is where fastboot is used. Going into recovery mode (by pressing the power button) doesn't help you here. This is where you have to figure out why fastboot isn't working. Sorry, this is an attempt at clarifying, but it doesn't help that fastboot is not working for you on that screen. And, so far, I'm not seeing anything obvious after trying different cables, different OSs, different ports. I'm hoping someone else will be more helpful. I assume you have enabled "developer options" on the phone and USB debugging is on and on first connect to a new computer you authorize the debugging connection on the phone on the popup that occurs when you do "ADB devices." These are all early steps in the instructions so I'm assuming everything went fine there. 1 Quote Link to post Share on other sites
claude0001 1,337 Posted January 28, 2023 Share Posted January 28, 2023 I agree with @Hook. That screen in the first screenshot should be shown while you use fastboot to flash the boot.img. adb, on the other hand, does its job only from recovery, not from that bootloader screen. That said, just flashing the Magisk-patched boot.img (which I understand is what you are trying to achieve) does not require any action to be performed from recovery. You should not go there at all for this. The no-command-screen usually indicates that the recovery image fails to boot. It normally should not be shown at any step of a reflashing procedure, and probably indicates that something has gone wrong in your flashing attemps. 2 Quote Link to post Share on other sites
kevg 14 Posted January 28, 2023 Author Share Posted January 28, 2023 Ahh, that's it, thank you! I ran fastboot right on the "START" screen and it worked. Even worked on my X270 without needing to boot up the Raspberry Pi. 2 Quote Link to post Share on other sites
kevg 14 Posted January 28, 2023 Author Share Posted January 28, 2023 My final steps to get to LineageOS: Install LineageOS: 1. Root the device: https://community.fxtec.com/topic/3690-pro1-x-rooting-with-magisk/ For "unauthorized" issues, see https://community.fxtec.com/topic/3788-stuck-on-step-12-of-root-pro1-x-via-magisk-cannot-run-fastboot-flash-boot/?tab=comments#comment-65246 1. Download from https://forum.xda-developers.com/t/lineageos-20-for-pro1-x.4543997/ lineage-20.0-20230127-UNOFFICIAL-pro1x.zip dtbo.img recovery.img vbmeta.img 1. Download ARM64 build of GApps for Android 13 for Mobile (*not* Android TV): https://wiki.lineageos.org/gapps#mobile 1. adb reboot bootloader 1. Only the *first time*, need to flash the recovery: fastboot flash dtbo dtbo.img fastboot flash vbmeta vbmeta.img fastboot flash recovery recovery.img fastboot reboot recovery 1. On START screen, fastboot reboot recovery 1. Factory reset 1. Format data/factory reset 1. Format data 1. Go back 1. Apply update 1. Apply from ADB 1. adb sideload lineage-20.0-20230127-UNOFFICIAL-pro1x.zip 1. Might get stuck at 47%, this is okay and just wait until it completes (see https://wiki.lineageos.org/devices/pro1/install#installing-lineageos-from-recovery) 1. Advanced 1. Reboot to Recovery 1. Apply Update 1. Apply from ADB 1. adb sideload MindTheGapps-13.0.0-arm64-20221025_100653.zip 1. Might get stuck at 47%, this is okay and just wait until it completes 1. Reboot system now Quote Link to post Share on other sites
claude0001 1,337 Posted January 29, 2023 Share Posted January 29, 2023 There is no need to root stock, just to install LineageOS. For that it would have been enough to just unlock the bootloader, no need for Magisk and boot.img patching ... On the other hand, if having root during use of the phone was your goal, you will find that in your newly flashed LineageOS, Magisk and su are now gone. You'll then have to re-install Magisk and re-do the boot.img-patching procedure (this time using the boot.img from payload.bin, contained in the lineage*.zip you used for sideloading). 2 Quote Link to post Share on other sites
kevg 14 Posted January 29, 2023 Author Share Posted January 29, 2023 Just now, claude0001 said: There is no need to root stock, just to install LineageOS. For that it would have been enough to just unlock the bootloader, no need for Magisk and boot.img patching ... On the other hand, if having root during use of the phone was your goal, you will find that in your newly flashed LineageOS, Magisk and su are now gone. You'll then have to re-install Magisk and re-do the boot.img-patching procedure (this time using the boot.img from payload.bin, contained in the lineage*.zip you used for sideloading). Ahh, interesting, okay. Thanks! Quote Link to post Share on other sites
Hook 3,015 Posted January 29, 2023 Share Posted January 29, 2023 (edited) Also, if all you want is root (SU) and you don't care about magisk modules, you can simply use the depreciated method of renaming the magisk file changing the .apk extension to .zip and then using adb sideload to flash it in recovery the same way you do MindTheGapps. I'm not sure you can't also still use Magisk modules that way, but since I don't use them, I can't say. I never even open the Magisk app, but it gives root to any app that asks permission and I say ok. Edited January 29, 2023 by Hook 1 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.