Jump to content

Recommended Posts

So I eventually decided that I might as well root my PrawnX, and tried to follow Casey's instructions here:  

https://community.fxtec.com/topic/3690-pro1-x-rooting-with-magisk/?tab=comments&_fromLogin=1

I got to the point of flashing the patched boot image back from my PC to the phone, and hit an error:

Quote

fastboot flash boot ./magisk_patched-25200_r5Hk7.img
target reported max download size of 805306368 bytes
sending 'boota' (98304 KB)...
OKAY [  2.317s]
writing 'boota'...
FAILED (remote: (boota_a) No such partition)
finished. total time: 2.334s

So then I did this:

Quote

fastboot getvar current-slot
current-slot: a
finished. total time: 0.003s

Made me a bit nervous, because Casey's instructions of the PDF suggest that the file flashes to boot_b automatically.

But whatever, I went with what getvar returned, and entered this:

Quote

fastboot flash boot_a magisk_patched-25200_r5Hk7.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [  2.320s]
writing 'boot_a'...
OKAY [  0.443s]
finished. total time: 2.767s

Then I did the "fastboot reboot", and voila, the PrawnX booted without problems, and I had superuser access through Magisk.

YMMV, but it all looks tickety boo.

Now I can get myself into some REAL trouble.

🙂

Edited by Name_not_avail
fixed the quotes
  • Thanks 1
Link to post
Share on other sites

Thanks. let us tag @Casey, so FxTec can check if there is something inaccurate in the guide.
(See below comments)

12 hours ago, Name_not_avail said:

So then I did this:

Quote

fastboot getvar current-slot
current-slot: a
finished. total time: 0.003s

Made me a bit nervous, because Casey's instructions of the PDF suggest that the file flashes to boot_b automatically.

 

Link to post
Share on other sites
5 hours ago, claude0001 said:

For the record: @Casey's instructions did work for me. It automagically flashed the right slot, which I think was "b" in my case.

Same for me...

I did it twice (before and after upgrading one of the beta versions). No errors for me so far.

  • Thanks 1
Link to post
Share on other sites

I don't see how I could have been in the wrong fastboot screen.  I didn't touch any of the buttons on the phone to change anything.

The phone was completely stock, and I followed the PDF instructions to the letter, with one exception:

I was using "Minimal ADB and Fastboot" to issue the terminal commands.  That's been on this PC for a few years for other Android projects, but I don't see that being likely to change anything.  Maybe, I guess.

I will be interested to hear from @Casey about the difference between slot a and slot b, and whether I have screwed something up for future phone mods.  Seems to work just fine at the moment, though.

Link to post
Share on other sites
45 minutes ago, Name_not_avail said:

the difference between slot a and slot b, and whether I have screwed something up

I think it is unlikely you damaged anything.

As you probably know, the A and B slots are a kind of safety net that (among others) allows the device to keep the previously running OS "in reserve" whenever an update is installed. The active slot basically flips between A and B everytime a new ROM is flashed. So whether A or B is the "right" one for installing Magisk simply depends on the number of previous flashings being even or odd.

Edited by claude0001
  • Thanks 1
Link to post
Share on other sites

I think the culprit can be identified by the difference here

18 hours ago, Name_not_avail said:

sending 'boota' (98304 KB)...
OKAY [  2.317s]
writing 'boota'...
FAILED (remote: (boota_a) No such partition)

versus

18 hours ago, Name_not_avail said:

sending 'boot_a' (98304 KB)...
OKAY [  2.320s]
writing 'boot_a'...
OKAY [  0.443s]

I have never heard of "boota" without an underscore. The big question is how it got in that weird state, but not most likely it was fixed by you changing:

18 hours ago, Name_not_avail said:

fastboot flash boot ....

to

18 hours ago, Name_not_avail said:

fastboot flash boot_a ....

Overwriting the weird value it had as read by "boot"....

 

  • Thanks 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

Terms