% fastboot boot astro_magisk_patched.img
Sending 'boot.img' (19128 KB) OKAY [ 0.500s]
Booting ERROR: usb_read failed with status e00002ed
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed
That's what I did - I flashed boot. I can probably share a root boot image if anyone wants it. I see no harm in that. It's the scatter file I can't share yet.
instead I took the brute force approach of dumping the entire ROM via SP Flash Tool and then using a hex editor to find the boot image.
mtkclient looks handy. What were the commands you used?
mtk r boot_a,vbmeta_a boot.img,vbmeta.img
Also, I'm curious - how did you locate it?
Almost exactly what's on the mtkclient github page (https://github.com/bkerler/mtkclient):Code: [Select]mtk r boot_a,vbmeta_a boot.img,vbmeta.img
The only difference there is using boot_a and vbmeta_a in place of boot and vbmeta. Although as it turns out, the vbmeta partition didn't need to be touched, so saving a backup was less important (although it never hurts).
Once the boot.img was extracted, I put it back onto the device with adb and then patched it with Magisk. Ignore the stuff on github about the mtk-specific Magisk. The official Magisk works fine.
I didn't know at the time that mtktool existed. It's definitely the better approach here.
It's pretty easy to find the header of the boot.img by searching for the right magic string indicating an Android boot image. Then the length of the partition I determined based on some output from SP Flash Tool, which I've long since forgotten. But I'm guessing that I got the length wrong, hence the initial failure.
Greetings, all! (I was a regular user of this forum a few years ago after getting my Gemini, but I dropped out once that was all set up. My Astro Slide arrived an hour ago — hurrah! — and so I'm back…)No Planet Computer support. From here is the only way. You can root it using the images and the procedures mentioned here. Banks will not work ( I am from Brazil ). And with the bootloader unlocked you will be in the orange state . The Astro will boot with this message and you will have to wait 5 seconds to boot. Please see the messages here.
What's the latest on installing rooted Android on the Astro?
I haven't found anything on any of the Planet sites (in fact, the obvious one (https://support.planetcom.co.uk/) doesn't even mention the Astro), and this thread is all I can find elsewhere.
I'd like to set up my Astro the same way as my Gemini: running rooted Android only. (I run Termux and sshd, edit /etc/hosts, and a few other things needing root. The down-side is that my bank's app won't work, but for me that's a price worth paying. On the Gemini it was a huge hassle, needing to reboot my Mac into Debian 9 to run Planet's Flash Tool — but I gather it's all different now…)
Is this possible? Is there an officially-approved way (or is there likely to be one soon)? Or is there a single, foolproof set of instructions?
There is no officially approved way (or, really, any sign of any support whatsoever from PC, but I digress...), but the images and procedures in this thread should work fine, as long as you are comfortable with what you're doing. I've been running mine rooted for several months now, with no problems.
Regarding your bank app, have you tested it with the newest Magisk, using the new DenyList feature? That should be generally much better about allowing picky apps to run, since they are put into a context where the phone actually is not rooted. While I haven't tried a broad range of apps, and almost certainly not your bank, I've yet to find an app that complains about root with DenyList.
some apps here in Brazil don' t work if you install Magisk, even if the phone is not rooted. For example : Bank apps, flying companies apps, insurance companies ( auto, life, etc )
You can root it using the images and the procedures mentioned here.
And with the bootloader unlocked you will be in the orange state . The Astro will boot with this message and you will have to wait 5 seconds to boot.
> mtk r boot_a boot.img
MTK Flash/Exploit Client V1.6.0 (c) B.Kerler 2018-2022
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
Thanks.some apps here in Brazil don' t work if you install Magisk, even if the phone is not rooted. For example : Bank apps, flying companies apps, insurance companies ( auto, life, etc )
Have you used the "Hide the Magisk app" feature in Magisk settings? I've seen some apps that look for the app by name, and if you just let Magisk rename itself, problem solved. :)
I was unable to get mtkclient to work on Mac. I don't know if it was a problem with my mtkclient install or with the Astro, but I gave up and installed it on a Linux machine and it worked perfectly there.Same with me. My Mac has dual boot ( Big Sur and linux ).
I was unable to get mtkclient to work on Mac.
Collecting shiboken6>=6.4.0.1 (from -r requirements.txt (line 7))
Could not find a version that satisfies the requirement shiboken6>=6.4.0.1 (from -r requirements.txt (line 7)) (from versions: 6.0.0a1.dev1606911628, 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.1.0, 6.1.1, 6.1.2, 6.1.3, 6.2.0, 6.2.1, 6.2.2, 6.2.2.1, 6.2.3, 6.2.4)
No matching distribution found for shiboken6>=6.4.0.1 (from -r requirements.txt (line 7))
Please edit requirements.txt and fill it with the versions less than your system. Even with these versions, it worked for me.QuoteI was unable to get mtkclient to work on Mac.
That's… frustrating.
As it happens, I do have one little headless box running Linux Mint — but that fails part-way through the ‘pip3 install -r requirements.txt’ step:QuoteCollecting shiboken6>=6.4.0.1 (from -r requirements.txt (line 7))
Could not find a version that satisfies the requirement shiboken6>=6.4.0.1 (from -r requirements.txt (line 7)) (from versions: 6.0.0a1.dev1606911628, 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.1.0, 6.1.1, 6.1.2, 6.1.3, 6.2.0, 6.2.1, 6.2.2, 6.2.2.1, 6.2.3, 6.2.4)
No matching distribution found for shiboken6>=6.4.0.1 (from -r requirements.txt (line 7))
‘pip3 install shiboken6’ installs version 6.2.4, which is clearly too low.
I'm guessing that may be because that needs python 3.7+ while I have python 3.6.9 — but ‘apt upgrade python3’ reports that as ‘already the newest version’. Is my installation too old? (/proc/version says ‘Linux version 5.4.0-135-generic (buildd@lcy02-amd64-053) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #152~18.04.2-Ubuntu SMP Tue Nov 29 08:23:49 UTC 2022’, but I don't know what most of that means.) I keep it up-to-date in Update Manager and/or apt — is there anything that those will miss?
Sorry if this is dumb stuff, but I know almost as little about Linux admin as I do about python or Android…
mtk r boot_a,vbmeta_a boot.img,vbmeta.img
…patch[ed] it via Magisk…
If I got it right, as allways, this wipes all your data?
Yes , unlocking and rooting the phone will wipe your data.If I got it right, as allways, this wipes all your data?
I think so. Others here can probably say for sure, but I'd certainly assume that such a big change can erase all your apps/data/settings and anything else you have stored on the phone, so before doing anything else, make sure you have backups of anything you want to keep! (I'll add that as a first step.)
Dom, if other people might benefit from those instructions, then I'd be very happy for you to post them elsewhere! (I don't mind about attribution, either way. I'm happy to take credit, though of course much of that was based on earlier work by Noppe, you, and others in this topic.)
And if you do, please post a link back here, in case we can learn from them too! A central knowledgebase is a great idea, and much needed.
(BTW, what does ‘CI’ mean in this context? A Continuous Integration server of some kind? I'm assuming it's not the Channel Islands, nor a Confidential Informant…)
you neglected to mention that the bootloader MUST be unlocked, otherwise the Astro will be soft-bricked until repaired.
you neglected to mention that the bootloader MUST be unlocked, otherwise the Astro will be soft-bricked until repaired.
s/neglected to mention/didn't know/ :)
In fact, I still don't fully understand… Do all Astros arrive unlocked, or was I just very lucky that mine wasn't?
And while it's great to include that on the wiki too, could you expand it into idiot-proof instructions like the rest — possibly including a line on what locking is, and how to tell whether an Astro is locked? (“You can do this by using Fastboot” is only helpful if you already know what Fastboot is, how to install it, and how to use it to unlock something — and if you already knew what, you probably wouldn't need to be reading the instructions in the first place!)
The wiki looks great otherwise — except that it doesn't seem to have any of the hyperlinks, which are pretty vital. I'd also suggest copying the bold highlighting too, though that's more subjective.
Do you get a message on the boot about 'Orange State'?No, nothing like that. As far as I can tell, the boot sequence looks the same as it did before rooting. (I can confirm it is rooted: I can su in Termux.)
I am surprised you did a root without unlocking the bootloader. Can someone explain this ? Thanks.Do you get a message on the boot about 'Orange State'?No, nothing like that. As far as I can tell, the boot sequence looks the same as it did before rooting. (I can confirm it is rooted: I can su in Termux.)
And I can't submit a PR coz I don't have the necessary knowledge to write it! (Also, I've only looked at the page on GitHub, not bothered to clone it and everything.)
But let's try to work it out. You said “You can do this by using Fastboot and the OEM Unlocking in Settings -> Developer Options”:
- Is that the program you can install with e.g. apt install fastboot?
- What would you type into it, and what would that do?
- On my phone, the latter is Settings → System → Advanced → Developer options → OEM unlocking. Is that the right one?
- I'm guessing that option needs to be enabled to unlock the phone? Is that also the right way to check whether the phone is unlocked?
- Do you need to do both the Fastboot and the OEM setting, or will either work?
Did it come pre-installed in Chinese or have Deejay-dota installed?
If you go to settings, about device you will see deejoy-dota. Please see my attachments, but it is in portuguese ( I am Brazilian )Did it come pre-installed in Chinese or have Deejay-dota installed?
Plain (British/UK) English. I don't know what ‘Deejay-dota’ is, but if it's an app, then it's not there!
I did turn on the Astro a few times before trying to flash it, so it's not impossible I might have changed that setting — but I don't recall doing so.
But Planet have always encouraged, or at least allowed, other OSs &c, so maybe it arrived unlocked?
Looking at `mtkclient`'s README, it _is_ necessary to unlock the bootloader before flashing an unsigned image.
I can't tell how it's possible to get past the unverified boot warning. I've edited the tutorial, but it's still important to unlock the bootloader before rooting or flashing non-OEM boot images.
The only conclusion I've come to is that Andy's Astro has had some sort of prior modification we're/Andy's not aware of. Possibly factory. Did it come pre-installed in Chinese or have Deejay-dota installed?
If you go to settings, about device you will see deejoy-dota. Please see my attachments, but it is in portuguese ( I am Brazilian )
(Yours) (Mine) … … Tempo em atividade Uptime 12:59:52 10:55 Versão Embutida Padrão Custom built version alps-mp-r0.mp1-V8.132_haocheng.r0mp1.k61v1.64.bsp_P20 alps-mp-r0.mp1-V8.132_haocheng.r0mp1.k61v1.64.bsp_P20 Deejoy-Dota Aktualizações de software System Update Verificar nova versão do software ──────────── ──────────── Número da versão Build number Astro-11.0-Planet-05182022-V01 Astro-11.0-Planet-05182022-V01 … …
I think it is a service to update android ( provided by PC ) but really don' t know.If you go to settings, about device you will see deejoy-dota. Please see my attachments, but it is in portuguese ( I am Brazilian )
I can see what look like the corresponding fields on my Astro in Settings → About phone — but there's nothing corresponding to ‘Deejoy-Dota’:Quote
(Yours) (Mine) … … Tempo em atividade Uptime 12:59:52 10:55 Versão Embutida Padrão Custom built version alps-mp-r0.mp1-V8.132_haocheng.r0mp1.k61v1.64.bsp_P20 alps-mp-r0.mp1-V8.132_haocheng.r0mp1.k61v1.64.bsp_P20 Deejoy-Dota Aktualizações de software System Update Verificar nova versão do software ──────────── ──────────── Número da versão Build number Astro-11.0-Planet-05182022-V01 Astro-11.0-Planet-05182022-V01 … …
(And what is ‘Deejoy-Dota’, anyway? Google finds only 5 results, of which this page is one, and the other 4 look like Japanese or Russian…)
I want to use rooted android.
D:\>adb reboot bootloader
D:\>fastboot flashing unlock
(bootloader) Start unlock flow
OKAY [ 21.063s]
Finished. Total time: 21.071s
D:\>fastboot flash boot_a boot-magisk.img
Sending 'boot_a' (40960 KB) OKAY [ 1.133s]
Writing 'boot_a' OKAY [ 0.195s]
Finished. Total time: 1.404s
D:\>fastboot reboot
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.009s
-----D:\>fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.003s
D:\>fastboot flashing unlock
(bootloader) Start unlock flow
OKAY [ 26.931s]
Finished. Total time: 26.939s
D:\>fastboot flash boot_b boot-v07-magisk-from-app-26300.img
Sending 'boot_b' (40960 KB) OKAY [ 1.318s]
Writing 'boot_b' OKAY [ 0.172s]
Finished. Total time: 2.121s
D:\>fastboot reboot
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.009s
D:\>adb shell
Astro:/ $ su
Astro:/ # exit
Astro:/ $ exit
As written above, I was able to be rooted Astro Slide on v07 without any problems, but when I carried out exactly the same procedure on the v07b, it fell into a boot loop. I cannot even power off.
I left it until the battery ran out and investigated with MTK client, the following rooted image for v07b seems to be incorrect. (Stock image is no problem.)
https://github.com/planet-community/planet-devices/wiki/Astro-rooting#rooting-methods
Writing with either FASTBOOT or MTK client, it fell into a boot loop in the same way. MD5 matches have also confirmed.
When I used a boot image patched with Magisk v26.4 from the v07b Stock image, I was able to be rooted successfully.
For reference, I put it here.
https://drive.google.com/file/d/1dCSZicKI14S2sYMS-gz5rceJ301xL9SQ/view?usp=sharing
MD5 3ea412192887d4b320d6a1f9770c903d
Supplementary information.
After the battery ran out, I connected the power supply while holding down the volume reduction button, and it booted in FASTBOOT mode.
This procedure was new knew to me.
Even without MTK client, the boot image can be replaced again.