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?
Related
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 everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
snOwjAwk said:
Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
Click to expand...
Click to collapse
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
zfk110 said:
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Click to expand...
Click to collapse
I tried to install twrp but ran into this error (on mac):
booting...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
EDIT:
Tried it from a windows pc now, got another error:
creating boot image...
creating boot image - 11765760 bytes
Sending 'boot.img' (11490 KB) OKAY [ 0.495s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Phalanx7621 said:
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Click to expand...
Click to collapse
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
snOwjAwk said:
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
Click to expand...
Click to collapse
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
zfk110 said:
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
Click to expand...
Click to collapse
Bootloader is unlocked! That's why im curious why it doesnt work...
snOwjAwk said:
Bootloader is unlocked! That's why im curious why it doesnt work...
Click to expand...
Click to collapse
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
zfk110 said:
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
Click to expand...
Click to collapse
That's what I did... And there was no other USB device connected other than the pixel. Fastboot devices also only showed my device
Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?
binarnh said:
Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?
Click to expand...
Click to collapse
Most likely the culprit is either out of date platform-tools or TWRP...
What version of adb, fastboot, & TWRP are you using? Also, how are you booting TWRP -- there have been many cases where people would use the command "fastboot flash boot twrp.img" instead of booting temporarily...
Hope this ends up being helpful as that means it resolves it...
Are you able to fastboot boot the latest twrp.img?
Might want to give Deuces script a whirl. I've seen this fix situations like yours.
ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...
binarnh said:
ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...
Click to expand...
Click to collapse
This might sound crazy, but, at least try another USB A to C cable, and other ports on your pc. The P2XL is notorious for being finicky when it comes to cables and ports. What might work for one phone, doesn't necessarily mean it will for the other. Make sure it's a 2.0 USB cable as well :good:
I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same
binarnh said:
I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same
Click to expand...
Click to collapse
Then it's likely a hardware/port issue would be my guess.
Meh, so I will look for a workshop nearby that will exchange the port for me and check later
I would also suggest that you re-download EVERYTHING...
You may be stuck with a "buggy" TWRP image file or platform tools....and/or go against conventional thinking and download and try an older version of TWRP to see if it does it at that point as well...
In either case, hopefully you get it figured out and good luck to you...hope this ends up being helpful!
There were a number of Pixel 2 XL's that did suffer from charging port issues, including my original. Luckily I was still under warranty and was issued a replacement. The phones would charge fine but data did not transfer as with adb/fastboot, nor would Android Auto work.
https://forum.xda-developers.com/pixel-2-xl/help/pixel-2-xl-charging-port-damaged-t3783638
Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"
binarnh said:
Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"
Click to expand...
Click to collapse
What fastboot command did you give?
Badger50 said:
What fastboot command did you give?
Click to expand...
Click to collapse
I use flash all script
binarnh said:
I use flash all script
Click to expand...
Click to collapse
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables
binarnh said:
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Not running platform-tools through power shell either are you?
What happens when you try double clicking on the flash-all.bat file with your mouse?
binarnh said:
Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Based on your error, I'm guessing all the files in the Full Factory .zip file (all 6 of them) aren’t residing there with the adb & fastboot .exe files within the platform-tools folder. Make sure you’re seeing those 6 files (you will have a two .sh files, two .img files, one .zip file, etc.) with the .exe adb & fastboot file.
Then, also make sure that you are directing your powershell or command prompt to the correct “platform-tools” folder, because many other people seem to have multiple “platform-tools” folders and they end up directing to a wrong folder…
Hope this ends up being helpful…
I fixed it! The error in fastboot mode probably came from a file that I extracted from winrar, when I downloaded the factory image again and extracted the files this time through 7zip and copied them to the platform-tools folder and double-clicked flash-all.bat fastboot started and the installation was successful! Thanks to everyone who wanted to help me solve this problem <3
ps. btw, I haven't replaced this broken port on the phone... just started working again...
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, I'm trying to root an Android 10 Alldocube tablet iPlay30.
I'm using this guide: https://www.getdroidtips.com/root-alldocube-iplay-30-magisk/
And so trying to unlock the booloader (using Win10) using ABD and Fastboot.
In the command prompt I write: "adb devices"
and win10 recognises the tablet. ok
I write: "adb reboot bootloader"
and ok the tablet reboots in FASBOOT mode
But then if in the command prompt I write: "fastboot devices"
The cursor wraps and nothing happens
If I write: "fastboot flashing unlock"
It appears the writing "<waiting for any device>" and nothing happens
Any help? Thank you!
Don't you try this link to configure the USB in FASBOOT mode, good luck. https://android.stackexchange.com/questions/46142/fastboot-doesnt-see-device/87392#:~:text=Reboot device into fastboot mode,unrecognized device in the list
KimLe said:
Don't you try this link to configure the USB in FASBOOT mode, good luck. https://android.stackexchange.com/questions/46142/fastboot-doesnt-see-device/87392#:~:text=Reboot device into fastboot mode,unrecognized device in the list
Click to expand...
Click to collapse
Thank you! I succeeded in unlocking the bootloader. Unfortunately when I put the patched (from Magisk) boot.img in the Rom file on the PC, and select the scatter.txt, Flash Tool says there is a checksum issue.
Any suggestion please? Thank you!
Can you tried this link from UMIDIGI. It is used ADB and FastBoot commands to install patched (from Magisk) boot.img for Android 10:
https://community.umidigi.com/forum.php?mod=viewthread&tid=19114&extra=page%3D1
KimLe said:
Can you tried this link from UMIDIGI. It is used ADB and FastBoot commands to install patched (from Magisk) boot.img for Android 10:
https://community.umidigi.com/forum.php?mod=viewthread&tid=19114&extra=page%3D1
Click to expand...
Click to collapse
Thank you.
Unfortunately it doesn't work
I suppose there is a problem with Magisk.
The last Magisk apk seems to generate correctly a file starting from the original boot.img and it calls it "magisk_patched_1HqYW.img"
So if I put it in the original ROM folder and then flash the boot with SP Flash Tool, it seems to go all ok, but the tablet isn't rooted.
If I use to flash it with ADB, it flashes the magisk file correctly ... but then the tablet is bricked. It doesn't boot and goes on and off in loop with the first image only.
Fortunately, flashing the complete original ROM with SP Flash Tool, it returns ok to factory status....
The bootloader is still unlocked but no way to root the device. I suppose, I repeat, for a wrong img file from Magisk.
Any solution? Magisk is the last version. So Magisk Manager 8.0.4
I see it's very different from the other past versions (from tutorial I can find around, I mean)
If someone knows also of other Alldocube tablets rooted recently, it could be good.
The iPlay 20 for example (with windows, not linux)
Thank you!
Albertohf said:
Thank you.
Unfortunately it doesn't work
I suppose there is a problem with Magisk.
The last Magisk apk seems to generate correctly a file starting from the original boot.img and it calls it "magisk_patched_1HqYW.img"
So if I put it in the original ROM folder and then flash the boot with SP Flash Tool, it seems to go all ok, but the tablet isn't rooted.
If I use to flash it with ADB, it flashes the magisk file correctly ... but then the tablet is bricked. It doesn't boot and goes on and off in loop with the first image only.
Fortunately, flashing the complete original ROM with SP Flash Tool, it returns ok to factory status....
The bootloader is still unlocked but no way to root the device. I suppose, I repeat, for a wrong img file from Magisk.
Any solution? Magisk is the last version. So Magisk Manager 8.0.4
I see it's very different from the other past versions (from tutorial I can find around, I mean)
If someone knows also of other Alldocube tablets rooted recently, it could be good.
The iPlay 20 for example (with windows, not linux)
Thank you!
Click to expand...
Click to collapse
Cause the Android 10 firmware, it is verified all module flash to it, so if you use SP Flash Tool the stock boot.img will replace your patched-boot.img upon reboot. So it need to flash the module files by ADB/Fastboot to disable-verity when it has been flashed. Those commands work well when I use them to root my Umidigi A9 pro Android 10.
KimLe said:
Cause the Android 10 firmware, it is verified all module flash to it, so if you use SP Flash Tool the stock boot.img will replace your patched-boot.img upon reboot. So it need to flash the module files by ADB/Fastboot to disable-verity when it has been flashed. Those commands work well when I use them to root my Umidigi A9 pro Android 10.
Click to expand...
Click to collapse
You are GREAT! It was my fault! I did not followed the instructions properly! iPlay30 rooted!
albyhf said:
You are GREAT! It was my fault! I did not followed the instructions properly! iPlay30 rooted!
Click to expand...
Click to collapse
Glad your iPlay30 Rooted.
albyhf said:
You are GREAT! It was my fault! I did not followed the instructions properly! iPlay30 rooted!
Click to expand...
Click to collapse
What instructions did you used?