Help me rooting the Go 10.3

[DanyDanman]

Posting this here to cover all bases. This time under the thread.

This is with the edl /lnowrite.bin

C:\Users\User>edl.exe /z
Found EDL 9008
<log value="ERROR: Start sector 8200 not allowed for LUN 0 through EDL Flash" />
Requesting reboot... ok

This is with edl /lA235F_LOADER_BIT5_Alephgsm_com.elf

C:\Users\User>edl.exe /z
Found EDL 9008, requesting reboot... ok

Perhaps this only a verbose thing but I post just in case.

[Renate]

Perhaps the answer is that this Firehose loader is just screwed up.
I'll look into this anomaly to see if there's any insight to be gained.

Have you ever seen that error elsewhere?

[Renate]

Hope springs eternal. Try the one in the PM.

[DanyDanman]

Originally Posted by Renate

Have you ever seen that error elsewhere?

Not before latest post, the one before this.

Originally Posted by Renate

Hope springs eternal. Try the one in the PM.

C:\Users\User>edl /u0 /r /pmisc misc.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting read misc.img... ok, reading 100% ok

C:\Users\User>edl /u0 /w /pmisc misc.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write misc.img... ok, writing   0%
Could not write device

C:\Users\User>edl /z
Found EDL 9008, requesting reboot...
<log value="ERROR: Read non multiple sector size value from USB 59 sectsize4096" />
No response

I have tested again so that last one is nu fluke. The base loader does not give any errors. (But must admit I am recently using /z.)

Fingers crossed

[Renate]

Originally Posted by DanyDanman

<log value="ERROR: Read non multiple sector size value from USB 59 sectsize 4096" />

Ah, I know what 59 means.

Try again, same URL, different file.

[DanyDanman]

You are a true genius.

C:\Users\User>edl /u0 /w /pmisc misc.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write misc.img... ok, writing 100% ok

Does this mean I can root my device?

[Renate]

Originally Posted by DanyDanman

Does this mean I can root my device?

Probably. Just do the Magisk.apk, patch boot, write it.

Before that, just do a double check that everything stays in sync.
Make sure that you can do commands after a write.
Just do stuff like:

edl /u0 /w /pmisc misc.img
edl /u0 /w /pmisc misc.img
edl /u /g
edl /u0 /w /pmisc misc.img
edl /z

[DanyDanman]

I will test today after work at the office. So somewhat later in the evening 7 PM ish.
If it's not clear I will double check with you.

Have good night.

[Renate]

Originally Posted by DanyDanman

I will test today after work at the office.

Ok. Don't quote it. Just say that everything went ok and normal.

[DanyDanman]

Could you write a short instruction for my use case?
I just want to be sure I don't mess thus up.

Or point me to the right instruction.

(Not home yet, so no rush)

[Renate]

Originally Posted by DanyDanman

Could you write a short instruction for my use case?

Huh? I don't know what you mean.

I want to make sure that after doing a write "/w" that the synchronization between the desktop client and the EDL server is preserved. That is, I want to see:

edl /u0 /w /pmisc misc.img
... ok
edl /u0 /w /pmisc misc.img
... ok

And not

edl /u0 /w /pmisc misc.img
... ok
edl /u0 /w /pmisc misc.img
df&(*9696&&^ ????

You know what a command is supposed to do know with /g, /r, /w, /z
I'm just asking you to mix it up a bit and make sure that individual commands work in isolation as well as proximity to others.
Just hit the up arrow and enter a few times.
It should take 10 seconds to do this. Don't quote it, just report any weirdness.

[DanyDanman]

Alright, that is clear. What I am after is how to write the boot after I have patched it. That part is clear.

[Renate]

I know that your abl/bootloader/fastboot doesn't have any flashing commands, but I didn't check if it had a boot command. It's always better to check a new image by booting before flashing.

fastboot boot Magisk123456.img

If it works or if it doesn't then you can proceed to flashing.

edl /lpatched.bin
edl /u /w /pboot_b Magisk123456.img
edl /z

Note: It could be boot_a or boot_b, The last I saw your system it was on b active.
You can do a "fastboot getvar all" or "edl /u /g" to see which slot is active.

[DanyDanman]

Posting it here so everyone knows:

C:\Users\User>fastboot boot boota_patched.img
Sending 'boot.img' (38708 KB)                      OKAY [  0.894s]
Booting                                            FAILED (remote: 'unknown command')
fastboot: error: Command failed

It's as we expected.

Everything went ok and normal. In other words I have root access.

My gratitude is huge. Hit me with a PayPal addresses for 2 cups of coffee.

Now going to test adding support for said app. (kanji study)